In the Default SLA Workflow, the last Timer activity transitions to both the End and another Create Event activity simultaneously, but the workflow does work.

However, presumably due to performance improvements in the workflow engine in Dublin, it is now possible for the workflow to End first, before the final Create Event activity executes. By design, transitioning to End stops the workflow and does not execute any more activities.

Steps to Reproduce


  1. Open the Priority 1 resolution (8 hour) SLA definition.
  2. Change the duration to 1 minute.
  3. Create a P1 incident by setting Impact and Urgency to High.
  4. After the SLA breaches, open up the task_sla record and view the workflow.


Starting with Eureka patch 4, the Default SLA workflow has been updated to wait for the activities to complete before the workflow ends.

To manually correct the workflow, check it out and make the following changes:

  1. Delete the workflow path from the final SLA Percentage Timer activity to the End activity.
  2. Link all of the Create Event activities to a new Join activity.
  3. Link both outputs of the new Join activity to the End activity.

This causes the workflow path to execute each step as expected prior to performing the End activity.

An example of the correct workflow in the Eureka release can be seen below:


Related Problem: PRB593926

Seen In

Berlin Hot Fix 4
Calgary Patch 7 Hot Fix 2
Calgary Patch 7 Hot Fix 5
Dublin EA 1
Dublin EA 7
Dublin EA 8
Dublin Patch 1
Dublin Patch 1 Hot Fix 1
Dublin Patch 3
Dublin Patch 7 Hot Fix 2
Eureka Patch 1
Eureka Patch 10 Hot Fix 1
Eureka Patch 11
Eureka Patch 12
Eureka Patch 13 Hot Fix 2
Eureka Patch 13 Hot Fix 5
Eureka Patch 2
Eureka Patch 4 Hot Fix 1
Eureka Patch 5 Hot Fix 1
Eureka Patch 7
Eureka Patch 8
Fuji Patch Hot Fix 1
Fuji Patch 11

Fixed In

Eureka Patch 4

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-08-25 15:44:42