Hi,
We have a connector that triggers an automation script whenever specific data changes by calling the ExecuteScript method like this:
The script is executed successfully in case of the following flow:
Interactive Automation Script -> InterApp Call -> Connector -> ExecuteScript
However, when the start of the flow is a User Defined API (Automation Script), instead of an IAS, it fails to execute the script because there’s no user cookie:
Would there be a way to make this work?
Thanks in advance.
Hi Jason,
As a workaround for the issue I would suggest to send an SLNetMessage as followed:
Hope this helps!
Kind regards,
Hi Jason,
Could you log the contents of the property ‘protocol.UserCookie’?
I believe that in certain instances it will contain a prefix that may need to be trimmed out before passing it to the automation script.
Hi Joao,
The user cookie looks like this in case it fails: 39D49F3E377C4B6D94AF5F4731C8052D:NO_INFORMATION
The user cookie is empty in case it’s triggered from an IAS.
Hi Jason,
Apparently, my recollection was slightly off as it was a suffix and not a prefix.
If you trim the :NO_INFORMATION out of the usercookie you should have valid GUID string, although not in the format we are most used to see it.
Could you try to manipulate the user cookie so that it removes everything after the : (including the : as well)?
Hi Joao,
That doesn’t seem to do the trick unfortunately.
Hi Stacey,
I can confirm that this workaround works.
However, the issue has been raised internally to have a closer look at the issue.