hey, so it looks like a dependent flow run has just disappeared… it’s not archived, just gone. 😕 it was a dependent flow from a flow of flows. the link to the flow run doesn’t load anything anymore, it just brings up a blank page. it’s also not in the list of runs for the flow, nor in the dashboard with the history of every flow run.

Hey @Martim Lobao, Cloud has a retention period of 2 weeks. Did literally 1 flow run disappear or quite a lot? Was it an old run?

1 flow that i’ve noticed, and it first ran 5 days ago

I can’t think of a reason why at the moment but will check with the team tomorrow. So we had a specific change lately where we fixed an issue. The issue was that flow versions were being cleared if the version of the Flow was bumped and the created timestamp of the flow was beyond the retention period. This logic was changed to only archive the version if all the runs were past the retention period (as expected). This seems different from the issue you are describing though. Could you show me a screen shot of your view so I know what page you’re looking at?

this is the page where the flow was

Hey @Martim Lobao - any chance you restarted the run after the latest Failed state? From my end, it looks like this flow run was restarted at • 2021-09-13 80730 UTC • 2021-09-15 140247 UTC And the last state I see for the run is Failed at 2021-09-15:59 UTC

hey @Zach Angell, correct, i had already previously restarted the flow twice before. it was just after that that the flow run disappeared

Thanks for your help here @Martim Lobao. It looks like there was a race condition where this Flow Run was deleted because the flow version was archived and it was in a "Scheduled" state. The system misinterpreted the Flow Run as a Scheduled version of a archived Flow version, which we would want to delete. We have a bug fix going out shortly and will keep you updated as it's released!

thanks @Zach Angell, please let me know when it’s fixed

@Martim Lobao - we just released a fix for this, please let us know if you see any other weird behavior. Thanks for your help in tracking down the bug!