Is anyone else having this problem?
Alot of my Cron workflows have a similar operation..
Trigger > Resource Block checks to see if there is anyhing to do >
yes --> Workflow Starts
no --> branch directs the workflow to a code block that hits a logging function and then stops. (in theory).. only lately.. a random block down the line will trigger anways and cause the workflow to error and fail and then I get notifications of failure.. even though it wasnt supposed to run in the first place?
it is BIZARRE.. im not sure what is up, whther its me, but lately the workflows all seem to be REALLY glitchy..
You can see in this screenshot.. Trigger starts, getCount checks to see if anything needs to be donem CheckForVenuesToUpdate triggers the LOG_ codeblock and that is supposed to be the end. I even tried adding a response block after the code block.. thinking maybe it was an issue with the codeblock? but that doesnt work.. then you can see that it skips 4 blocks (which are critical for the workflow to operate) and then randomly starts that loop block (which fails because there is nothing to loop through).
When i trigger everything manually.. its fine.
This is a visual of what is happening:
The only thing I just thought of when writing this, is that the loop block that keeps triggering for no reason, is a loopv2 .. I havent upgraded all of the loops in this workflow to V2.. most of them are v1, but there are 2 more v2 blocks in this workflow (3 in total) but the other two dont seem to be having any issues. I've tried deleting the loop block and starting from a fresh one.. but no change.
Any ideas out there?
