PrefectClient
offers methods to simplify common operations against Prefect’s REST API that may not be abstracted away by the SDK.
For example, to reschedule flow runs, one might use methods like:
read_flow_runs
with a FlowRunFilter
to read certain flow runscreate_flow_run_from_deployment
to schedule new flow runsdelete_flow_run
to delete a very Late
flow runget_client()
returns an asynchronous client to be used as a context manager, but you may also use a synchronous client.
PREFECT_CLIENT_CUSTOM_HEADERS
setting. This is useful for adding authentication headers, API keys, or other custom headers required by proxies, CDNs, or security systems.
User-Agent
- Managed by Prefect to identify client versionPrefect-Csrf-Token
- Used for CSRF protectionPrefect-Csrf-Client
- Used for CSRF protectionScheduled
state with a delay. This is useful if you accidentally scheduled many
flow runs of a deployment to an inactive work pool, for example.
The following example reschedules the last three late flow runs of a deployment named
healthcheck-storage-test
to run six hours later than their original expected start time.
It also deletes any remaining late flow runs of that deployment.
First, define the rescheduling function:
View the complete example
N
completed flow runs from your workspaceN
completed flow runs from your workspace, use read_flow_runs
and prefect.client.schemas
.
This example gets the last three completed flow runs from your workspace:
View the complete example
DeploymentFilter
to get the last three completed flow runs of a specific deployment.
get_client
to set multiple runs to a Cancelled
state.
This example cancels all flow runs that are in Pending
, Running
, Scheduled
, or Late
states when the script is run.
View the complete example