@Marvin I created an automation to cancel a flow after 4 hours running, but it doesn't work for one flow. I used a tag, added to all flows and define an automation based on the tag. what is wrong?

I found a couple of GitHub issues related to automation and cancellation, but they may not directly address the specific issue you are facing with a particular flow not cancelling as expected. Below are the three issues I found that appear to be most relevant: 1. Cascading cancellation for normal subflows, not just sub-deployments: This issue relates to a behavior where parent flow cancellation does not cascade down to child flows properly under certain conditions, although it's specifically about subflows and may not be directly applicable to your case. 2. Support retrying flows on crashed state: This discusses a behavior where flows retry infinitely when crashing due to inherent errors, highlighting potential issues with automation and the

retries

parameter, which again might not directly address your specific issue. 3. Prevent running late runs after some threshold: This one discusses a different feature request concerning late flow runs, which isn't about cancellation but could be loosely related to automation logic. None of these issues seem to specifically address a problem with an automation that cancels a flow after 4 hours of running based on a tag. This might indicate that your issue could be unique to your configuration or might not have been reported yet. To further assist, I would need some more information: - The exact logic you used in your automation rule for cancellation. - Any error messages or logs indicating why the automation may not have worked as expected. - If there's anything unique about the flow that does not get cancelled compared to others. Feel free to provide additional details if possible, and we can explore further.

Hey anna - can you DM me some more information? A screenshot of the automation and the url of the flow run? Thanks.