Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Lifecycle event issue

_Gaurav
Kilo Sage

Hi Folks!

 

While setting up a lifecycle event, I ran into a problem where, depending on the conditions, I had to create more than 150 activities/tasks for my LE. This required me to create more than 50 activity sets, which takes time to submit the case and sometimes prevents the LE from being attached to the case.
Even with the activity container it didn't function well.

If someone faced the same issue or has any suggestions on how to overcome the issue, please share.

 

Thanks in advance!

17 REPLIES 17

In this case try using Advanced conditions to trigger activity sets and apply audience criteria on the activities. Trigger only those activity set and activities which are absolutely important at the time of case creation.

 

You can also reach out to ServiceNow support by raising a case with them and take their inputs on addressing this issue. 

michaelj_sherid
ServiceNow Employee
ServiceNow Employee

Hi @_Gaurav  I agree with @Sandeep Rajput in execution of the activity sets. It appears that you are triggering them at once is this correct? I am curious to know more on your use case, but as Sandeep mentioned, support is certainly a path to take if you are having issues.

 


Regards,

Mike

Hi @michaelj_sherid 
I am not triggering all the activity sets at once. The trigger type of the first activity set is 'Immediate' however the rest of the activity sets are dependent on each other.
As mentioned, I have 51 activity sets in an LE which is taking time to execute and sometimes prevents the LE from being attached to the case by giving an error as 'StackOverFlowError'

Hi @_Gaurav  I recommend to submit a Hi Support issue to see why this is happening. This is the fastest way to get help with an issue like this where there are many moving parts. 

 

Regards,

Mike

Appreciate, your suggestion @michaelj_sherid, I will do the same to fix the issue ASAP.
Thank you.