Is anyone else experiencing a high number of executions getting halted or stuck without throwing a timed out error or anything.
In the past we have experienced flo’s getting stuck at the end of processing and not passing the completed back up to a main flo. This issue being manageable as we could trust the flo to complete but just not return the completion values.
Now I am experiencing an error where the flo is getting stuck part way through an execution and not moving onto the next card which is causing all sorts of chaos. for example
If creating new issues in Jira from Smartsheet entries and not then updating the smartsheet row I have a large amount of duplicate issues in my Jira each time the flo runs.
If transition issues from changes in smartsheet records is complete but the smartsheet record is not updated. I now get what could only be called spam email from all the items that have been transitioned but the smartsheet record not being updated correctly. (A change in the flo when this scenario happens to update the ss but I should not have to) this control is in place to ensure that Jira users do not transition an issue they are not supposed to not error fix uncompleted flo executions’s
Thanks for any help