I have a workflow where data is submitted to a Tulip Table in Step 1 via eSign. That same trigger that adds data also has a transition step to Step 2. On the step exit of Step 1, we clear/reset the variables.
There might have been connectivity issues of some sort that caused a delay in this eSign trigger, but the record is being added with the cleared/default variables (so it shows empty or with default value). The Record History also shows that the data is being added in Step 2 instead of Step 1, which is not correct based on what was built.
My initial though is that the transition to Step 2 somehow happened before the data being added. And so On Step Exit already cleared the data. on the eSign in Record History, all the variables value show correctly.
Hello team, I was wondering if there’s any insight on this.
Hi @chieumaihong - apologies for the delay here, but I was checking with our internal team to get some of their advice as well.
It is tough to fully understand if this is a bug or just a flaw in how the logic is set up without going into the app (which we can do if you want, but just would need to make this a support ticket).
Some things you can do to further debug this behavior without making a support ticket:
- Separate the triggers - Instead of having one eSign trigger that both adds data and transitions steps, split these into separate actions with controlled sequencing. Add a message after each action to display so you can see that the trigger executed successfully.
- Move variable clearing - Instead of clearing variables on Step Exit, consider clearing them at the beginning of Step 2, after data has been recorded
Give these a try and let us know what you see!
We do have a support ticket initiated last Friday (#25588) and have not heard back for further discussion. Since we’re in a pharma space and this incident raisedconcerns regarding the data being missed on the PROD instance by our Quality Rep, so we’re now in the investigation phase to understand the failure mode and cause of it. We have also executed about 700x of these workflows, and this is the first time it happened. I was also not able to reproduce it, so it’s a little tough to try what you have mentioned above.
Understood - I have flagged this to our support team and will have someone get back to you quickly!
1 Like