I'm encountering this issue regularly with flows that run for 4+ hours. As the issue describes, the flows continue to run, but this leads to orchestration issues with parent flow/subflow relationships between deployments where the parent flow is waiting for a subflow to finish that the agent is no longer tracking. Is there anything I can do to prevent this?
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.
