Workday errors in plain English.

Submit an Error
errors / peci / picof-soap-fault-governederror-http-406-launching-integration

PICOF SOAP Fault governedError HTTP 406 When Launching Integration

✓ Verified PECI / PICOF 1 lookups
The error The following unexpected error has occurred: error from returned HTTP status: 406 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <SOAP-ENV:Fault xmlns:wd="urn:com.workday/bsvc" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>SOAP-ENV:Server.governedError</faultcode> <faultstring/> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

What it means

The PICOF integration returns a raw SOAP fault, SOAP-ENV:Server.governedError, over HTTP 406, with an empty fault string. This is Workday's generic governance/throttling fault. It fires when the request hitting the integration's endpoint is being rejected before it reaches normal business validation, most often due to a security or governance policy blocking that specific request.

Troubleshooting

  1. Check the integration system user's security group and domain access for the PICOF integration to confirm it still has the permissions the integration needs.
  2. Look at recent tenant-level changes (security policy updates, IP allowlist changes, or governance rule changes) around the time the fault started.
  3. Try the same integration run against a different, known-good integration system user to isolate whether the fault is user-specific or integration-wide.
⚡ Quick fix

Re-run the integration with an integration system user known to have full, unrestricted access to confirm whether the governedError is permission-related.

✓ Permanent fix

Document and lock down the exact security group and domain grants the PICOF integration user needs, so future security policy changes don't silently strip access and trigger this generic fault again.

Was this helpful?

Related errors