Skip to main content
K
koppulan659741
February 26, 2026
Question

work item canceled

  • February 26, 2026
  • 3 replies
  • 0 views
Recently, there was a production server outage, and several process instances went into an error state at an XOR gateway, showing the message “Work item cancelled.”
We manually resumed the affected instances from a point after the gateway, and they continued running. However, when the flow reached the same XOR gateway again, the instances failed once more with the same cancellation message.

    3 replies

    stefanhelzle0001
    stefanhelzle0001
    February 27, 2026

    Do you see any additional info in the log files?

    shubhama926776
    shubhama926776
    February 27, 2026

    As per my understanding Outage caused processes to run as deactivated user; swimlane Run As overrides the manual initiator, blocking XOR gateway permissions. Update swimlane Run As to active user

    mikes0011
    mikes0011
    Brainy
    March 2, 2026

    If you have deactivated users that certain instances were started "as", my normal trick is to reactivate those user account(s), rename them to something meaningful only to me, add them to the "service accounts" group, and remove their email address.  This prevents any original user from logging into them or taking them back over, yet they still run processes fine.  Over time, once legacy instances are gone, go around and remove those legacy service accounts.

    Terms & ConditionsAccessibility statement