I have a concern about the timing of workflows versus actions and would like to know if my concerns are valid and how to avoid problems.
I am designing a process whereby a user selects DaySheets from a list view and an Action adds UserEmail() to the [Select] Column of the DaySheets worksheet - this works well so far
Then I have a Group Action that does the following:
My concern comes from research I did yesterday that shows that my Actions and Workflows are triggered from different locations, namely the Client and the Server. For my mechanism to work the Workflow needs to be triggered immediately after step 2, and certainly before step 4 is completed. If it is triggered after step 4 has finished, there wonโt be any records with a valid [Select] flag.
Am I right to be worried, and if so, how can I fix it? Invoicing is too important not to be reliable.
Solved! Go to Solution.
I would say, the behavior you seen on action/workflow is as it is. That s how Appshee action and workflow behaive.
Very much roughly to say, Action is a job on the client side. while the workflow is server-side jobs.
When you hit the action to change data etc, you will immidiately see the changed value as it is happening on the client side. Then app start to push the data to your backend data source, so it is always time lag between your device and server.
To the contrary, once the data change is reaching out to your data table, then workflow is firstly triggered as this data change event is only detected at server side.
To make sure that all the arrangements you made to works as you expected, I would sugget you try first not to include the last action to chagne the value to a group action. Just remove it.
Then on your workflwo setting, you have to send email workflow first. Then add second task/action after that, to change the value . Firing your action not from Action, but fire from workflow.
Im not sure how workflow will behaive, async nature or not, but it s worth testing.
As a matter of time Automation will be in full swing. Then you probably have another option to call process (to send email) first and chain another process to change the value under a single bot to do the same job. For this Automation, following process should not be executed, meaning the second process to change the value of your data will not happen untill the first process of sending email to executed. I m not perfectly sure but bot with the chained process will act in async nature.
Just invite Automation specialist for opinions.
User | Count |
---|---|
38 | |
34 | |
27 | |
23 | |
17 |