docs/v3/api-ref/cli/flow-runs.mdx
prefect flow-runsprefect flow-runs [OPTIONS] COMMAND [ARGS]...
prefect flow-runs inspectprefect flow-runs inspect [OPTIONS] ID
prefect flow-runs lsprefect flow-runs ls [OPTIONS]
$ prefect flow-runs ls --state Running
$ prefect flow-runs ls --state Running --state late
$ prefect flow-runs ls --state-type RUNNING
$ prefect flow-runs ls --state-type RUNNING --state-type FAILED
prefect flow-runs deleteprefect flow-runs delete [OPTIONS] ID
prefect flow-runs cancelprefect flow-runs cancel [OPTIONS] ID
prefect flow-runs retryprefect flow-runs retry [OPTIONS] ID_OR_NAME
The flow run can be specified by either its UUID or its name. If multiple flow runs have the same name, you must use the UUID to disambiguate.
If the flow run has an associated deployment, it will be scheduled for retry and a worker will pick it up. If there is no deployment, you must provide an --entrypoint to the flow code, and the flow will execute locally. </Info>
<AccordionGroup> <Accordion title="Arguments" defaultOpen> <ResponseField name="ID_OR_NAME" type="string" required> </ResponseField> </Accordion> <Accordion title="Options" defaultOpen> <ResponseField name="--entrypoint"> The path to a file containing the flow to run, and the name of the flow function, in the format `path/to/file.py:flow_function_name`. Required if the flow run does not have an associated deployment. </ResponseField> </Accordion> </AccordionGroup> <Note> **Example:**$ prefect flow-run retry abc123-def456-7890-...
$ prefect flow-run retry my-flow-run-name
$ prefect flow-run retry abc123 --entrypoint ./flows/my_flow.py:my_flow
prefect flow-runs logsprefect flow-runs logs [OPTIONS] ID
prefect flow-runs watchprefect flow-runs watch [OPTIONS] ID
prefect flow-runs executeprefect flow-runs execute [OPTIONS] [ID]