+1I have got a workflow rule that runs on an update to risk/issues, counting the total # of open risk/issues (by status) from the parent project. The counts returned are incorrect when the workflow runs it, but noticed that if it simply runs a second or two later it is correct.
What’s the best way to incorporate a pause or delay to avoid this problem?
+4Hello Daniel -
To incorporate a pause or delay in your workflow rule to avoid incorrect counts, you can consider the following approach:
Scheduled Workflow Rules: You can set up your workflow rule to run at a scheduled time rather than immediately upon update. This can be done by selecting a specific date or time frame for the rule to execute. For instance, you could schedule the rule to run a few seconds or minutes after the update occurs, allowing time for the system to stabilize and reflect accurate counts.
Repetitive Runs: If the workflow rule needs to run repetitively, you can set it to run at regular intervals, such as daily or weekly. This ensures that the rule checks the counts periodically, potentially catching any discrepancies that occur immediately after an update 1.
Here's the article for reference - https://success.planview.com/Planview_AdaptiveWork/Configurations/Business_Rules#h_29379c25-982a-4e92-9459-9e29d7a1817d
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
