Thanks for the tip - do you have any examples of how to use xtk.persist.Write() with a memo field? As you can see above I couldnt get the xtk.session.Write() to work with the memo field so had to hack the sqlExec() together as a workaround

Managed to do it via sqlExec, but interested to know why the above xtk.session.Write method wouldn't worktry { sqlExec("insert into oritempdata (sbitly,sedmLink,sIrDescription,mIrMessage,sswitchDocumentId,sserviceOrderId,sworkflowId) values ('" + data.bitly + "','" + data.edmLink + "','" + data.Ir...

I have a temporary schema that has a bunch of normal attributes and a memo element. When I use xtk.session.Write with an XML object, the attributes update fine, but the memo element (IrMessage) is blank. Any idea how to template in an XML element in the JS?   <!-- Key Fields --> <attribute label...

Where did the timezone change?If you change the timezone in the workflow or the scheduler, you need to restart the workflow for it to take effect

Yes this could be your issue. When you google the error message "The message has expired;" you get results like this: https://community.smartbear.com/t5/SoapUI-Open-Source/The-message-has-expired/td-p/103117

Can you elaborate on why AA with API call takes too long to run?After setting up Launch/Analytics/Triggers/Pipelined for abandoned cart, direct AA/AC calls would be my preference as it is relatively simple to set up.That said, Triggers does give you quite a bit of flexibility on triggering rules as ...

We had to do this - you can easily do it in a workflow using a query and update activity Query and UpdateSet Targeting to Operators Query the Operators you want Update the Operators timezone CheersDarren

The 500 error is coming from your destination system. It looks like your request is working but the system you are requesting data from is throwing a 500 error. The hints will be in the nested exception details.Issues like this during auth can occur when system clocks are out by too much, etcI would...

By default scheduler timezone is set to "_inherit_" so if you provide the users with workflow templates set to their timezone, the scheduler activity should inherit that timezone without any user intervention.

Not sure why you would want a List-Unsubscribe in an Alert activity as Alerts are usually used to target Operators of the instanceIf you do, then you need to use operator.id as Alerts use Operators, not Recipients as the targets