PICOF Failed to Find External_Pay_Group After Tenant Migration
What it means
After migrating a PICOF integration into a new tenant, the launch parameter still references a Pay Group by its Workday ID (WID) captured in the source tenant. WIDs are tenant-specific, so that identifier does not exist in the target tenant, and the integration fails to resolve the External_Pay_Group reference for every pay group in the launch parameter.
Troubleshooting
- Compare the launch parameter's Pay Group selections between the source and target tenant configurations rather than assuming they carried over correctly.
- Confirm whether the integration runs cleanly for the same pay groups in the source tenant, which points to a migration/reference problem rather than a data problem.
- Check the target tenant's Pay Group business objects directly to see whether the referenced WID exists at all.
Re-select each Pay Group in the launch parameter directly inside the target tenant so Workday regenerates a WID valid for that tenant, instead of relying on the migrated reference.
As a standing step in any future tenant migration or refresh, re-point every launch parameter that references a Pay Group (or any other WID-based object) inside the target tenant, rather than assuming object migration preserves those references.