Using version 2023.9.8:
In a workflow triggered by a Before Update event, I have been using an error block to prevent update of the record if certain conditions are not met. This has been working, but with the new version, it appears that the error block is not stopping the update from occurring. You may want to check this out.
I may have found the problem, but this workflow was working before I upgraded to 2023.9.8. Is there any reason why an oldRecord.values. would not be recognized in a Before Update workflow?
If you run it manually through the workflow builder you have to provide the proper params. Otherwise you wont have access to things like record/oldRecord and so on.
But could be something else. I just checked this(2023.9.8) and I get the values normally.
Well, it’s still ignoring the Error block on the workflow. I don’t have any interactive prompts in the workflow. Any thoughts on why this might be happening?
I suggest you try a simple Trigger → Error workflow and confirm that the beforeUpdate and Error steps are working correctly. It says your workflow is “deferred” which is the reason for your problems.
You cannot have a Deffered, beforeUpdate workflow. Deffered means it can wait, beforeUpdate must not wait.
This is written here Workflows :: Corteza Docs
In the grey square.
OK, I rebuilt the workflow from scratch, and the Deferred status did not appear. Successfully tested the workflow, so it works now. I can’t think of what caused the Deferred status to appear. Deleting some non-blocking prompts from the old workflow (which I did not include in the new one) did not remove the deferred status from the old workflow.
Can a workflow be placed in Deferred status for a reason other than its construction?
Prompts and Delay steps are always considered deferred (even non-blocking, since it still waits for the user to see the prompt before continuing).
That explains it. So, keep all prompts for After Create events, then?
For all things that can’t be prevented (with an error step or similar).
Also, beware that if you have an unconnected prompt/delay step in your workflow, it will also be deferred.
