PECI Fails: Tenant Not Enabled to Run a Data Initialization Service That Utilizes Effective Changes
The error Your tenant is not enabled to run a Data Initialization Service that utilizes Effective Changes.
What does "Your tenant is not enabled to run a Data Initialization" mean in Workday PECI?
PECI builds its output from an effective-change stack, and that capability is switched on per tenant rather than per integration. When the switch is off, the integration stops before it extracts anything, even though the configuration itself is untouched.
Quick fix
Switch the run to a full extract rather than an effective-change extract so today's file can still be produced, then move back to effective changes once the tenant is confirmed enabled.
Permanent fix
Add a check for effective-change Data Initialization Service enablement to the post-refresh checklist for every tenant that runs PECI, and re-verify it after each tenant build, because the setting does not survive a refresh taken from a tenant where it was off.
Troubleshooting
- Confirm which integration actually failed. The message names the Data Initialization Service, not the parent PECI integration, so the failing object in the log is often not the one you launched.
- Check whether this is the first run after a tenant refresh, a migration, or a Workday release. The enablement is tenant-scoped and does not travel with a configuration migration.
- Run the same integration in a lower tenant and compare. If identical configuration succeeds in one tenant and fails in another, the difference is enablement rather than setup.
- Review the integration's effective-change settings and confirm it is genuinely configured to use effective changes rather than a full-file extract.
- Ask Workday Support to confirm whether the effective-change Data Initialization Service is enabled for the failing tenant, naming both the tenant and the integration system.
Was this helpful?