Skip to main content

Change orders created before Release 2638 fail to activate with SELF_REFERENCE_FROM_TRIGGER

Some change orders created before the September 23 package update can't be activated. A workaround is available.

Status: Workaround available. Permanent fix in progress.
​Affected release: Production Release 2638
​Started: September 23, 2026, about 05:00 UTC

What's happening?

After Production Release 2638 was installed on September 23, some change orders can't be activated in Salesforce. When you try to activate one, you see an error that contains:

SELF_REFERENCE_FROM_TRIGGER

This only affects change orders created before the update. Orders created after the update activate normally.

How does this affect me?

Affected orders stay in Draft, so the subscription changes and billing updates they contain are delayed until the order is activated.

Your data is safe. The error stops the activation before anything is saved, so the order stays exactly as it was. Nothing is lost or changed.

How do I fix it?

To resolve this:

  1. Open the order (or its quote) in Nue.

  2. Click Save and Exit without making any changes.

  3. Activate the order as usual.

Re-saving refreshes the order so it activates normally.

Why did my Order Total change after re-saving?

You may see a small change in the order's standard Salesforce Order Total. This is expected. Re-saving corrects how summary line totals are added up. It does not change the price of any line or the amount you bill.

What if the error doesn't go away?

If the error persists after re-saving, or you'd like us to handle it for you, contact Nue Support with the order number and we'll take care of it.

What is Nue doing about it?

A permanent fix is being prepared for an upcoming package update so this can't happen again.

We're sorry for the disruption. We'll update this article when the permanent fix is released.

Did this answer your question?