Call object is taking older execution's Run ID

[Siddharth V]

Hi Team,

 

One of our jobs did not complete successfully on Oct 31st with the Run ID (29946189). As a result, the corresponding call object triggers an alert without an attachment in the email.

 

The issue is that the call object is still using the same Run ID (29946189) from Oct 31st, and the client continues to receive emails without attachments.

 

Oct 31st Old Call Object report:

 

Nov 20th Old Call object report:

 

We thought it might be a bug and tried duplicating the call object and assigning it to the same job, but we are still facing the issue.

 

Nov 26th New Call object report:

 

Screenshot of call object's setting:

 

 

Could you please let me know why we are getting the same Run ID for all executions in the call object and how to fix this? Also, let me know if any additional details are needed.

 

Thanks!

Siddharth V

[Stephane Laflutte]

Hello Siddharth

I don't think it's normal for your activator to always have the same RunID.

Maybe there is an issue with the read buffer?
:READ function have some limitations


You could try &$ACTIVATOR_RUNID# instead of &UC_CAUSE_NR#

Hope it will be useful

Stéphane