I am encountering the following situation where I need to execute two Data Actions (DAs) within the same story. The logic for each of these DAs has been tested and the results have been verified. Both DAs are configured to interact with a table in the story containing percentages. When I modify these percentages and run the first DA multiple times, it consistently performs as expected without encountering any issues. However, when I switch to the second DA, it fails to execute in alignment with the changes made to the percentages in the table (pointing to different combination). This behavior persists even if I reverse the execution order.
No error message is presented, the DA Monitor reflects that no records were affected, so it seems it is not executed.
After repeated executions, I have noticed that saving the second DA, even without introducing any changes, acts as a catalyst for the correct execution and produces the desired results.
Thanks in advance
Thank you Nikhil, It indeed seems like a glitch.
Would like to update that at some point I suspected that maybe the fact that one DA was saved from the other might have something to do with this behavior (although I see no reason).
I have created a new DA and copied the steps to the new one.
Now it works ..
Looks like a glitch.
So If I get it right, DA 1 works on some input on the Table and produces right results after iterations. DA2 does not take into account the changes made in table. Does your DA2 work off the results produced by DA1? Can you check if it works properly if you publish the data and then run DA2. May be the code line of DA1 and DA2 along with the table will help in better understanding the issue.