Core Connector: Organization Outbound Fails to Launch on the Agent (Missing Web Service Access)
What it means
The Core Connector: Organization Outbound integration failed to launch on Workday's integration agent with only a generic failure message and no further detail. The connector calls the Get Organizations web service operation internally to pull its source data, and the launching ISU didn't have security access to that operation, so the job never got past its own setup step to produce a more specific error.
Troubleshooting
- Confirm the failure happens immediately on launch, before any output file or meaningful progress appears in the integration event, since a security gap on the connector's underlying web service call fails this early.
- Check the launch parameters against the connector's admin guide to rule out a plain configuration typo first (collection, connector name, tenant).
- Identify the underlying web service operation the connector calls to source its data (Get Organizations for Organization Outbound) and check the launching ISU's security group for access to that operation's domain.
- Grant the missing access, activate any pending security policy changes, and relaunch the same run to confirm the job completes instead of failing at launch again.
Grant the launching ISU's security group Get access to the Organizations web service domain (or the equivalent domain for the specific connector), activate pending security policy changes, and relaunch.
When standing up a new Core Connector, identify every underlying web service operation it calls internally, not only the connector's own Integration Build and Event domains, and grant the ISU's security group access to all of them up front, since a missing grant on an internal call surfaces only as a generic agent launch failure with no specific field or object named.