Issues applying multiple data actions in a custom action in a script

[mibaile]

We've been running into strange inconsistencies getting data actions to apply inside of a custom action in scripts. Today, for example, I have a script which currently has 3 data actions that are working. I determine I need to run one more instance of that last data action with slightly different variables. I add a small delay step and a new instance of the data action using copy, update one of the variables, save (in both places - on the custom action and the script itself), publish and run a test. The previously working instance of the data action no longer work with an unknown error. The data action itself is fine - I can run it with the same variables over and over regardless of what the last state was. I can understand if we typo the data in the variable or something causing the second instance of the action to fail, but the first one should still work (which it doesn't based on checking the data that should have updated via the api explorer). I'm hoping maybe there's some method to applying changes to scripts that I'm missing somehow.

[tim.smith]

Are you able to get correlation IDs from the failing data action responses in the script? If not, please open a case with Genesys Cloud Care to investigate further; we cannot access customer-specific data via the forum, meaning I can't search the logs to try and find the requests if you're unable to provide the correlation ID but Care has a higher level of access to sensitive data.

[mibaile]

Tim,

Thanks for responding. We do have a case with Care and they are looking into it. Doing more troubleshooting on this its seems there's a chance we're occasionally running up against formatting issues in the data as it gets passed to the data action, though it does seem a bit odd that the format a data action would stop working when nothing about the format changed. However, we've been working alot with putting in static data into some of our data actions such as Agent or Queue Ids and such using 'text expression' or 'interpolated data'. For example using a Queue ID with a setting 'text expression' seemed like at times would work if we simply placed the Queue ID in with no quotes (text expression seems to add them on its own from what we can see working with things like alert or info banners). If we go into our data action and put the queue ID in with no quotes it works, we figured it would be the same thing as using test expression for these other steps and so it would work - then we'd add another step with the same data action but different queue ID and both stop working. Kind of wild. But we are finding we are having good luck using variable data and simply passing the data to the action that way instead (setting the value in architect and passing as a variable). Using this method seems pretty fool proof so far. If you have any insight or know of any docs that cover for matting expected for interpolated or text expression that would be great - just confirm what is truly expected, if there are characters that need to be escaped etc. We're new to the platform so we could just be making errors in applying thigs and making false assumptions on occasion as well. To me the formatting explanation for issue makes the most sense.