Flow Transaction Cancelling at Approx 4 Hours
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2023 06:15 AM
I'm having a consistent issue across multiple instances in which a flow is becoming state CANCELLED after approximately 4 hours. The flow runs asynchronously, and executes large numbers of SQL queries via a script include which is called by the flow's action script. This is why it takes >4 hours.
Is there some form of transaction quota limiting the duration here or known limitation? It is strange that on many instances I am seeing a hard limit of 4 hours for my flow to run.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2023 08:02 AM
I'm wondering if maybe it is related to this system property. I found the info here
|
com.glide.cs.fdih.interactive.timeout |
Specify the length of time, in seconds, before the Flow Designer Integration Hub action workflow times out.
|
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2023 08:32 AM
Thanks for the reply Brian! I don't think it's related to this since it is not Interaction Hub nor is the limit specific to 4 hours. The weird part about this is that the Flow doesn't stop at 3 hours and 58 minutes, nor 4 hours and 5 minutes. It's near-approximately 4 hours every time give or a take some seconds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2024 02:30 PM
@acostello did you find the solution for this? I am facing the same issue.
