@Marvin Hey, I have a sub-flow run in late status. But, how can a sub-flow be late? The schedule I have is only for the parent flow. Thanks!

The information returned doesn't directly answer the question about why a sub-flow would have a 'late' status, particularly when only the parent flow is scheduled. Usually, a 'late' status might indicate that a run has not started at its scheduled time. Since I didn't find a straightforward explanation in the documentation, let's troubleshoot this issue a bit. Assuming the parent flow has been scheduled and triggers sub-flows as part of its execution, there might not be a separate schedule for the sub-flows themselves. However, if the sub-flow is somehow being tracked against a timing expectation or if there is an implicit expectation set by the start of the parent flow, it might incorrectly be marked as 'late' if it doesn’t start within a certain timeframe. To clarify this behavior and provide an accurate solution, I can look for information or reported issues related to this in the Prefect GitHub repository. Shall I proceed with that?

@Marvin yes

I found a relevant issue that might explain the behavior you're experiencing with the sub-flow being marked as late. The issue Agentless execution cannot trigger child flow runs, only the parent flow run (#5509) discusses a scenario where sub-flows are not being executed as expected during an agentless execution. Though this issue does not explicitly mention a sub-flow being marked as 'late', it could be related to your problem if the sub-flow is not executing properly or at the expected time. The discussion indicates challenges with the execution of sub-flows, which might manifest as a status issue. If the sub-flow's execution depends on the parent flow, and the parent flow's execution is delayed or not triggering the sub-flow correctly, it might cause the sub-flow to be in a 'late' state, especially if the system anticipates the sub-flow to run directly following the parent flow's trigger. Unfortunately, there is no direct mention of a sub-flow being in a 'late' status without having an explicit schedule. If this doesn't resolve your question and if the issue persists, I recommend reaching out on the Prefect community channels or opening a new issue in the Prefect GitHub repository with detailed information about your flow setup and the observed behaviors.

@hagai are you using run_deployment to kick off that subflow?

@Nate yes, exactly like that

so if the work pool for the deployment you're triggering with

run_deployment

doesnt have a worker running, then

Late

would make sense

Sounds reasonable. Thanks!