Hi there, seen some undesirable behaviour around 500 handling in flows. A request to create a flow run during a subflow run failed due to a 500 from the (self-hosted) prefect server. The flow in question is still marked as running, which is not the case. Interestingly, this subflows parent is also a subflow which is still marked as running - however the "root" flow is marked as crashed.

Hello Robert, would you be able to share the error with a full traceback here?

Hi, yes of course

I’ve had this happen to me several times. From my experience, this happens if flows fail during setup. Sadly, I can’t really provide a solid minimal reproducible example

I believe the 500 was caused by a time out on the orion DB, so I upped the timeout limit and seems to have worked. The real issue is that these flows should have been marked as crashed or failed, not stayed as running.

Glad it worked by increasing the timeout limit @Robert Hales. Are you able to open a bug report issue at the repo with that information?

Sure!