Flow Designer Issue – DocuSign Task State Not Reflecting Latest Update in Lookup Step
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
In our flow(screenshot attached below), we are handling a DocuSign task as part of an Employee Relations (ER) case process. Here's the intended flow:
1. Step 19(screenshot attached below): Lookup the state of the DocuSign task.
2. Step 20: If the state is Closed - Rejected, proceed to Step 21.
3. Step 21: Update the ER case state to Ready to allow the ER agent to regenerate the DocuSign task.
4. The ER agent previews and generates a new DocuSign task.
5 .If the manager signs the DocuSign task, it gets closed(if manager choose option decline to sign the state of docusign task is closed rejected), and in Step 22, the ER case is auto-closed.
6. In Step 23, the flow loops back to Step 19 to check the updated state of the DocuSign task.
Problem:
After the DocuSign task is regenerated and completed (either signed or rejected), the flow loops back to Step 19. However, the lookup in Step 19 does not reflect the latest state of the DocuSign task. It continues to return the initial Closed - Rejected state, even after the task has been updated (e.g., signed in the second attempt).
As a result, the condition in Step 20 always evaluates to true, and the flow never enters the else path, even though the task state has changed.
Requirement:
We need a way to ensure that Step 19 fetches the most recent state of the DocuSign task, not a cached or previously stored value. This is critical for the flow to correctly evaluate the condition in Step 20 and proceed accordingly.
