Hi Anna,
Is it possible that flow heartbeat issues with externally executed jobs (as described above) can cause CPU to drop to 0 while maintaining “Running” status for the flow in the cloud UI?
Using Prefect 2.x in a hybrid setup, I was running into an issue using ShellTask where the pod CPU usage would drop to 0 after a prolonged period of no (outbound) API communication to the Cloud (ie. a lack of DEBUG | prefect.client - Connecting to API at ...). This problem was averted by generating logs regularly, leading to regular outbound communication, which led to the flow to maintain processing and therefore finish properly.