Workday errors in plain English.

Submit an Error

Payroll Connector Fails: An Organization With WID Value Was Not Found for the Pay Group

✓ Verified PECI / PICOF 3 lookups
The error The following unexpected error has occurred: An Organization with WID value of <WID> was not found - <WID> = WID for US company pay group

What does "The following unexpected error has occurred" mean in Workday PECI?

The payroll connector points at a specific organization by its internal Workday ID, and that ID does not exist in the tenant where the integration is running. Workday IDs are unique to a tenant, so a value that was valid where the integration was built means nothing anywhere else.

Quick fix

Re-select the pay group in the integration attribute from inside the failing tenant so it stores that tenant's own reference, then relaunch.

Permanent fix

Reference organizations by a stable reference ID rather than by WID wherever the configuration allows it, and add a post-migration step that re-points every organization-valued integration attribute in the target tenant before the first live run.

Troubleshooting

  1. Take the WID from the message and look it up in the failing tenant. If nothing resolves at all, the reference is stale rather than a security problem.
  2. Check whether the integration configuration was migrated from another tenant, restored from a backup, or copied with Object Transporter. A migrated integration attribute holding a hard-coded WID is the usual cause.
  3. Review integration attributes, integration maps, and any launch parameter that names an organization or a pay group, noting which store a reference rather than a looked-up value.
  4. Confirm the pay group still exists and is still active in the failing tenant. A deleted, inactivated, or superseded organization produces the same message.
  5. Compare against a tenant where the integration succeeds and diff the organization-valued references specifically, rather than the whole configuration.
Was this helpful?

Related errors