Lifecycle Event not triggered as expected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 03:10 AM
I have created a HR Service and mapped it to a lifecycle event. Lifecycle Event has one activity set which is supposed to trigger immediately. After creating HR Case accordingly, the lifecycle event did not trigger as expected. Does someone have an idea what is missing?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 03:52 AM
Yes to both
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 04:01 AM
And if you check the event logs, can you see any other HR event being triggered?
(event logs are stored for limited period, I guess 7 days or so only)
Debugging tip - create a copy of what you have, remove the conditions or change it to anything else, then try to re-trigger to find out whether it can be with the event or something else.
(or if you don't mind modifying the triggers directly, no copy needed)
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 05:44 AM
As mentioned above in the other reply the fulfillment type as well as the BR to trigger lifecycle events seem to be missing, but I have no idea why that is the case
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2025 06:00 AM - edited 07-01-2025 06:00 AM
Hello @Julia Baus ,
Can you please send a screenshot of your preboarding activity set and the activities included within it for better clarity?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 03:23 AM
I see that you have created the required services and cases is getting created. It seems your record producer is not correctly mapped with the required service.
Check if your record producer has below script:
Thanks