Skip to content

Add events and resources reference documentation#21375

Merged
chrisguidry merged 2 commits intomainfrom
cloud-3632-events-reference
Mar 31, 2026
Merged

Add events and resources reference documentation#21375
chrisguidry merged 2 commits intomainfrom
cloud-3632-events-reference

Conversation

@chrisguidry
Copy link
Copy Markdown
Collaborator

@chrisguidry chrisguidry commented Mar 31, 2026

We didn't have any reference documenting the actual events Prefect emits — just the concept page explaining what events are. This adds a new "Events" section under API Reference that catalogs every event from OSS, Cloud, and integrations.

Each event is documented with its name, when it fires, resource ID pattern and labels, related resources and their roles, and payload fields. The section covers:

  • Flow run and task run state transition events
  • Deployment, work pool, and work queue lifecycle events
  • Worker and runner execution events
  • Artifact and asset lineage events
  • Concurrency limit slot events
  • Automation trigger and action events
  • Infrastructure events (blocks, pull steps, transfers, plus Docker/Kubernetes/ECS from integrations)
  • Prefect Cloud events (audit log, security, managed execution, billing, webhooks, incidents)

Also adds cross-links from the existing events concept page and the API reference overview.

We didn't have any reference documenting the actual events Prefect emits —
just the concept page explaining what events are. This adds a new "Events"
section under API Reference with pages covering every event from OSS, Cloud,
and integrations, including resource labels, related resources, and payloads.

Closes CLOUD-3632

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions github-actions bot added the docs label Mar 31, 2026
@chrisguidry chrisguidry marked this pull request as ready for review March 31, 2026 18:38
@mintlify
Copy link
Copy Markdown

mintlify bot commented Mar 31, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Prefect 🟢 Ready View Preview Mar 31, 2026, 6:40 PM

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d7ed7041a1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Task run state events only include tags as related resources, not the parent
flow run or flow.  The flow_run_id is in the payload's task_run object instead.
Also adds the run-count and orchestration resource labels and the task_run
payload field that were missing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Member

@desertaxle desertaxle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the existing API reference docs have a mechanism to keep them automatically in sync with the code as it changes. It would be great if we could have something similar to keep these pages up to date.

@chrisguidry
Copy link
Copy Markdown
Collaborator Author

@desertaxle Yeah I was trying to figure out how to approach that, do you think a CI task with an LLM making followup PRs makes sense? Or have we had good success with skills + guidance in the repo?

@chrisguidry chrisguidry merged commit c1c14fe into main Mar 31, 2026
7 checks passed
@chrisguidry chrisguidry deleted the cloud-3632-events-reference branch March 31, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants