prefect.flow_run.late
Flow runs starting lateDimensions:None
Available on:Native (1)
Interface Metrics (1)
Technical Annotations (29)
Configuration Parameters (4)
marklateruns.loop_intervalrecommended: 5.0 secondsprefetch-secondsrecommended: 120PREFECT_API_SERVICES_LATE_RUNS_AFTER_SECONDSserver.services.late_runs.loop_secondsError Signatures (2)
MarkLateRuns tooklog patterncannot find a heartbeaterror codeCLI Commands (2)
prefect agent start --hide-welcome -q default -p default-agent-pooldiagnosticprefect agent start --prefetch-seconds 120 -q k8sdiagnosticTechnical References (21)
src/prefect/workers/base.pyfile pathPENDINGconceptMarkLateRunscomponentprefect.server.services.marklaterunscomponentsupervisordcomponentdocker-in-dockerconceptscreencomponentagentcomponentflow runconceptnotificationcomponentlate stateconceptwork poolcomponentwork queuecomponentRUNNINGconceptCANCELLINGconceptSCHEDULEDconceptBase Job ManifestcomponentMarkLateRuns servicecomponentLate stateconceptPrefect AgentcomponentScheduled stateconceptRelated Insights (11)
Flow runs stuck in PENDING state after worker crashcritical
▸
Missing pipeline metrics delay data quality issue detectionwarning
▸
MarkLateRuns service execution exceeds loop intervalwarning
▸
Agent heartbeat failure due to docker-in-docker resource exhaustioncritical
▸
Prefect agent freezes in background screen sessioncritical
▸
Flow late-state notifications fail when agent is unresponsivewarning
▸
Flow runs stuck in Late state due to missing worker subscriptioncritical
▸
Work pool concurrency limit blocks agent from picking up late runs when PENDING runs accumulatecritical
▸
prefetch-seconds flag does not provision Kubernetes infrastructure earlywarning
▸
Flow runs not starting on time trigger Late statewarning
▸
Agent API connectivity loss delays scheduled flow runswarning
▸