How to Retrigger a Completed Activity Set Multiple Times in Lifecycle Events HRSD??

[meghanacn0606]

We’re working with Lifecycle Events in ServiceNow, and have a use case where a manager may want to retrigger a specific Activity Set multiple times, even after it has been completed.

For example, the Activity Set might include onboarding tasks or compliance checks that need to be repeated periodically or on-demand. Once the Activity Set is marked as completed, is there a way to retrigger it again for the same user, possibly multiple times, based on the manager’s request?

Key questions:

• Is there a native way to reassign or reinstantiate a completed Activity Set?
• Can this be done manually or via Flow Designer?
• Would we need to duplicate the Activity Set or use scripting to simulate retriggering?
• How can we ensure the activities don’t conflict with previous completions?

Any suggestions, best practices, or examples would be greatly appreciated!

[Wessel van Enk]

Hi @meghanacn0606,

Can a completed Activity Set be reassigned natively?

No, not directly. Once an Activity Set is marked as completed, ServiceNow does not offer a native "retrigger" button or built-in method to restart it for the same Lifecycle Event Case.

What you can do is manually create a new Lifecycle Event Case and assign the same Activity Set again.

Can this be done via Flow Designer?

Flow Designer alone cannot retrigger a completed Activity Set. But, you can use Flow Designer in combination with scripting to launch a new Lifecycle Event Case and assign the Activity Set.

Do you need to duplicate the Activity Set or simulate retriggering?

You don’t necessarily need to duplicate the Activity Set. You can use scripting to simulate retriggering by creating a new case and assigning the same Activity Set again. This is often done via UI Actions or custom Flow logic. If you do not want a new case, yes, then you need to duplicate the activity sets.

How to avoid conflicts with previous completions?

To prevent overlapping or confusion use unique Lifecycle Event Cases. Also, avoid duplicate task names and use advanced triggers by using scripts to check for prior completions and only launch if conditions are met.

I've build quite some lifecycles, but not being able to retrigger OOB or being able to even trigger activities within an activity set based on conditions is quite annoying. The products works well, but still has some flaws.