Hey
@Verun Rahimtoola,
Whenever I’ve encountered this, it usually indicates resource constraints in your execution environment if you are running a large flow/processing a lot of data OR network constraints if communication is blocked back to your GraphQL service, but I would also check to ensure you’re running the latest version of Prefect just in case.
Normally, the
Lazarus process should kick in to mark these tasks as Failed eventually if the tasks can reach Running, so the fact that they never reach this state leads me to believe one of the issues listed above is responsible.