Posted Mar 23, 2026 5:10 PM PDTUpdated Mar 24, 2026 10:26 AM PDTRetirement date: Mar 24, 2027
Open
| Alert type | Product defect |
| Release | 2026R1 |
| Using Workday | Accounts Payable, Procurement, Source to Pay |
| Product | Spend Management |
| JIRA | SMORDER-77551 |
| Affected Data Centers | All Data Centers |
| Workaround | For requisition auto-source issues, manually sourcing can be used to ensure Purchase Orders are created. Unfortunately there are no workarounds for the other two issues at this time. |
| Resolution Information | Next UpdateTue, 03/24/2026 – 17:00 America/Los_Angeles (GMT-0700) |
We are aware that users may be encountering intermittent issues in the following areas:
- Auto Souring requisitions — Auto-source completes but no Purchase Order is created
- Receiving Purchase Order — Stack Trace Error including the following message: java.lang.IllegalStateException: Duplicate target change
- Processing Supplier Invoiced associated to Purchase Orders — Supplier Invoice gets stuck in Draft status
Our development team is actively reviewing this with priority. We urge you to ensure Purchase Orders have been created for requisitions that should auto-source once the process is complete to ensure there are no disruptions with ordering. Manually sourcing will work if the Purchase Order is not created.
We will continue to provide updates on this alert as we get more information. The next update will be today, Tuesday March 24 at 5pm America/Los_Angeles (GMT-0700)
We apologize for disruptions this may be causing and appreciate your patience as we work to resolve this issue.