@Marvin can I find a flow by the flow id in the UI?

According to the Prefect documentation, every time you run a flow, it is tracked by the API server and displayed on the same UI page, which should help with debugging and observability. However, the excerpts obtained do not explicitly state how to find a flow by its flow ID in the Prefect 2.0 UI. For more specific instructions, I would recommend checking the Prefect documentation for a detailed guide or exploring the Prefect UI, as it typically provides an interface to inspect flows, including search or filter functionalities that may allow you to locate a flow using its ID. If you need further assistance navigating the UI to find a flow by its ID, please let me know, and I can provide more detailed guidance.

@Marvin what do I do when my flow get stuck at

cancelling

state?

what do I do when my flow get stuck at

cancelling

state?

@Ka Wing Fong did the infrastructure get deleted?

When your flow gets stuck in the 'cancelling' state in Prefect 2.0, you can attempt to cancel the flow run from the command line in your execution environment using the Prefect CLI. The command you would use is

prefect flow-run cancel

, followed by the ID of the flow run:

bash
$ prefect flow-run cancel 'your-flow-run-id'

Alternatively, you can cancel a flow run from the UI by navigating to the flow run's detail page and clicking the 'Cancel' button in the upper right corner. The cancellation process should move the flow run to a "Cancelling" state, and the agent monitors the state of flow runs and detects that cancellation has been requested. The agent then sends a signal to the flow run infrastructure, requesting termination of the run. If the run does not terminate after a grace period (default of 30 seconds), the infrastructure will be killed to ensure that the flow run exits. This process is designed to be robust and provides a strong guarantee of cancellation. It's important to note that this cancellation process requires that an agent is running to enforce the cancellation. If you notice that the cancellation does not happen after these steps or if the flow run remains stuck, it is advisable to consult the Prefect community on Slack or raise a Github issue to get further assistance. Let me know if you need more help with this issue, such as raising a Github issue or exploring other potential solutions.

our k8s task keeps on getting stuck at

ImagePullBackOff

hmm can you check the pod logs for the worker?

Failed to pull image "us-docker.pkg.dev/shiftsmart-api/ssm-data-pipeline/ssm-data-pipeline:None": rpc error: code = NotFound desc = failed to pull and unpack

Seeing this error but we never set the tag to

None

in our CI 😞

or

describe

a pod thats stuck in ImagePullBackOff?

I'm not sure. We always set an image tag to a sha. I'm trying to figure out a way to kill those k8s task. Not sure why they keep on spinning back up

can you just delete the k8s job? and you’re seeing successful jobs with the same image tag? id guess that None is not a valid image tag and it’s stuck trying to pull the image

Not the same image tag. The current image tag is a valid one

are you killing the pod or the job?

the pod