Activity Set Context stuck in 'Awaiting Trigger' even if the dependend Activity Set is in finishedIssue Under certain circumstances, an Activity Set Context state might be stuck in "Awaiting Trigger" state even if its depended Activity Set is in Finished state and any other trigger conditions have met. This behaviour usually manifests itself on Lifecycle Event cases spanning multiple months or years. ReleaseAll releasesCauseAssuming that Activity Set "AS1" has a dependency on Activity Set "AS2" and an arbitrary date, it is possible that, even after AS2 is in Finished state and the selected date is passed, AS1 might remain in 'Awaiting Trigger' state and never move to 'Running Activities' state. Looking at the Activity Set Execution for AS2, you will notice that the related Workflow context field is empty (despite the field being mandatory): The OOB Table Cleaner for the "wf_context" table is set to 15,552,000 seconds (180 days)https://instance_name.service-now.com/nav_to.do?uri=sys_auto_flush.do?sys_id=552f483c0a0a0b900082121e6ea5b65e This means that any wf_context that ended more than 180 days are being deleted. The Lifecycle Event logic behind the HR Activity Set Trigger Check workflow requires the wf_context of the dependent Activity Set's Activity Set Execution in order to check whether it has finished or not. If AS2 moved to Finished state more than 6 months before the selected date, its related wf_context would get deleted, causing the relationship between "AS1" and "AS2" AS to break, so the Lifecycle Event won't be able to progress. ResolutionIf your Lifecycle Event cases are expected to last for more than 6 months, you could update the 'Age in seconds' value of the above table cleaner (System Maintenance > Table Cleanup) to make sure the wf_context records for any active LE Case does not get deleted.