Activity Set in state of Launched but Activities not appearing in Lifecycle Case

aguanci57911335
Tera Contributor

Hi All,

 

We have a Leave Request Lifecycle Event Case with 3 Activity Sets. The 2nd Activity set is triggered after the first activity set is completed. However in this case the 2nd activity set Activities do not appear in the case and Activity Status shows them as "Launched." 

 

What could cause this to happen? I tried to find some documentation on this but could not find anything. I have attached a picture of the Activity Set Context. Please let me know if there is anything else I should provide to help find a solution for this issue. 

 

aguanci57911335_0-1746126386322.png

 

2 REPLIES 2

Abbas_5
Tera Sage
Tera Sage

Hello @aguanci57911335,

 

When an activity set in a ServiceNow lifecycle case is in the "Launched" state but the activities within it aren't appearing, it usually indicates a problem with the Activity Set's definition or the conditions for triggering itThe most common cause is that the Activity Set might be referencing a non-existent Activity, often because the Activity was deleted while the Lifecycle Case was still in progress.
 
Troubleshooting steps:
1. Activity Set Definition:
  • Missing Activities:
    Check the Activity Set execution record and the Activity Status records. An activity might be referencing a deleted activity, causing it to appear "launched" but not appear in the case. 
     
  • Incorrectly Specified Conditions:
    The conditions (audience, triggering events, etc.) for launching the activity set might not be correctly configured or might not be meeting the criteria of the current case. 
     
  • Audience Issues:
    If the activity set has an audience defined, ensure the user associated with the case meets the criteria. 
     
2. Triggering the Activity Set:
  • Event Triggering:
    If the Activity Set is triggered by an event, verify that the event is being fired correctly and that the Activity Set is configured to listen for that event. 
     
  • Workflow Conditions:
    If the Activity Set is triggered by a workflow, ensure the conditions in the workflow are met and that the workflow is executing as expected. 
     
  • Sequential Dependencies:
    If the Activity Set is supposed to trigger after another Activity Set, ensure the previous Activity Set is completed and that the conditions for the next Activity Set are met. 
     
Troubleshooting Steps:
  1. 1. Review Activity Set Execution:
    Go to the Activity Set Execution record and inspect the Activity Status records to see if any Activities are referencing non-existent records. 
     
  2. 2. Evaluate Conditions:
    Check the conditions and scripts associated with the Activity Set, especially if it's a "Combination" type. 
     
  3. 3. Examine Triggering Events:
    If the Activity Set is triggered by an event, verify that the event is being fired and that the Activity Set is configured to listen for it. 
     
  4. 4. Verify Workflow:
    If the Activity Set is triggered by a workflow, ensure the conditions are met and the workflow is executing correctly. 
     
  5. 5. Check Audience:
    If the activity set has an audience, confirm that the user meets the criteria. 
     
  6. 6. Restoration of Deleted Activity:
    If an Activity has been deleted, reinstate it within the Activity Set. 
     
Additional Notes:
  • For Activity Sets with "Other Activity Sets" or "Combination" trigger types, they might remain in "Awaiting Trigger" indefinitely. 
     
  • Consider using the advanced option instead of the combination if you are encountering issues with conditions. 
     
  • The workflow responsible for launching activity sets evaluates the conditions and scripts every four hours.

If it is helpful, please hit the thumbs-up button and accept the correct solution by referring to this solution in future, it will be helpful to them.

 

Thanks & Regards,

Abbas Shaik

Jordan Mo
Tera Contributor

Have you since been able to resolve this issue? Did you locate a workaround, we are also experiencing the same problem.