PRB1084321 & PRB664759 are connected, in order to talk about one we need to talk about the other


  • When submitting a request in the Service Catalog or kicking off a new workflow, the window may hang or experience very slow performance.
  • When loading a sc_req_item list with the Stage column showing, the list may take a longer than expected time to load or be cancelled by transaction quotas. Note: this is only slow if the sc_req_items loaded in the list have an impacted workflow.

What versions are impacted by performance issues related to PRB1084321 and PRB664759?

  • IP6 and earlier
    • Impacted by PRB664759
    • What types of workflows are specifically impacted? Big & complex workflows that contain pipes, |, in the sequence field. This behavior has always been in the platform, no regression
  • IP6 - IP8, where the regression happened
    • Partial impact by PRB664759, but regression introduced by fix causing PRB1084321
    • Additional information about the fixes/regression:
      • Part of the fix for PRB664759 is to run a fix script to clean up the impacted workflows, any using pipes in their sequence field, however, customers can still get affected workflows through updates sets, the Store, etc. For this reason they are not fully protected by this fix.
      • Additionally, the fix for PRB664759 introduced PRB1084321 where small, uncomplex workflows can now experience the reported performance issues
  • IP9+
    • Both PRBs are fixed and workflows with pipes should no longer experience this particular performance issue whether they are small or big/complex. We clean and evaluate the sequence on run time therefore eliminating the issue.

How can I proactively check if my instance is impacted?

Navigate to the following list to see all workflow versions that have a | in their sequence field and stage rendering is either Legacy or Requested item renderer:
Note: These are all of the potentially impacted workflows and the workaround should be applied.  Performance issues vary in severity, so depending on the complexity of the workflows, the issue may be varying degrees. 

Steps to Reproduce


There are multiple ways to determine if you are being impacted by this issue:

  1. View Requested Item in list view causes window to hang or cancels transaction. 
    • Try to configure the personalized list layout and remove the Stage field.
    • If the list displays afterwards, then this may be the issue.
    • Check succeeding steps to confirm. 
  2. Filter the list to specific catalog items. Re-add the Stage field.
  3. If issue appears for certain catalog items, locate and open the corresponding published workflow version for the catalog item.
  4. Verify if the XML file, via Show XML, contains |, pipe character, for full_sequences and expected_sequences fields. 


  1. Open this url:
    https://<instance url>/wf_workflow_version_list.do?sysparm_query=checked_out_by%3Djavascript%3Ags.getUserID()%5EORpublished%3Dtrue%5EGOTOfull_sequencesLIKE%7C%5Ecolumn_renderer%3D007c2f021b020100adca1e094f0713b4%5EORcolumn_renderer%3D2acd1c538f111200d95374f137bdee20
  2. Take note of the resulting workflow versions.
  3. While displaying the Requested Item with Stage field in list view, filter-out the catalog items using the workflow versions from above result. If the Requested item list view is now displaying, then you are experiencing this issue.


1. Open this url:
https://<instance url>/stats.do

2. Locate the Default thread running the impacted transaction.

3. Open the corresponding thread into a new window and refresh the page so the stack trace for the processing thread is visible.

4. Check if the below line is consistently seen in the stack trace while the thread is hanging/processing slow. Refresh the browser window to see what lines are being executed over time in the stack trace:



1. Import the attached UI Action, PRB1084321_UIAction_workaround.xml. This UI Action updates the sequence fields on all impacted workflow versions.

2. Navigate to /wf_workflow_version_list.do to see the new UI Action at the bottom of the list

3. Click the Update Sequence Fields UI Action to apply the workaround to all impacted workflow versions

4. We have also seen some workflow versions that are corrupt.  EX. They do not contain any activities or they do not contain a Begin.  Those will error out and cannot be updated.  

  • Advise deleting them as they cannot execute in that state regardless.

5. Run the following script in Background scripts to verify you have updated all versions that contain a pipe in the sequence fields.

var count = 0;
var verGR = new GlideRecord("wf_workflow_version");
while (verGR.next()) {
    if (verGR.full_sequences.indexOf('|') != -1 || verGR.expected_sequences.indexOf('|') != -1)

Additional Information

  • If new impacted workflows are imported/created, re-run the UI Action to reapply the workaround
  • Remember to test first in a development instance
  • This UI Action contains the same logic for the fix that was applied in this problem so there is no risk

Related Problem: PRB1084321

Seen In

There is no data to report.

Fixed In

Istanbul Patch 9
Jakarta Patch 2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-03-19 14:01:01