Hello Prefect Team, Overnight a scheduled job failed to fire - it remained stuck in pending. There are no logs or any indication why this has happened. Cancelling the job and re-running a new instance, it works just fine. Did something break overnight?

hi @Cormac - what kind of work pool was it? i.e. was it managed infra or your own? if it was managed infra, can you DM the flow run ID as well as your account and workspace ID?

@Nate very sorry to only reply now. for some reason my slack failed to notify me of your response. job ID no longer available. I'll re-raise if the issue occurs again. Details: • Our own workpool: Push Workpool • Triggers task over AWS FARGATE: This is our own infra, not managed

no worries! let us know if you see it again