Workday errors in plain English.

Submit an Error

"The Task Submitted Is Not Authorized" on Integration Launch

✓ Verified Core Connectors 5 lookups
The error The task submitted is not authorized for this user. Integration cannot be launched.

What does "The task submitted is not authorized for this user" mean in Workday Core Connector?

The account trying to launch the integration doesn't have rights to it. Launching an integration is a secured action - the user or ISU needs access to the integration system object and the Integration Event domain, separate from any web service permissions.

Quick fix

Grant the launching user's security group access to the Integration Event domain for that integration system, activate pending changes, and re-launch.

Permanent fix

Schedule integrations under a dedicated service account that never gets deactivated. Document the grants. Add a launch-permission check to the offboarding checklist so departing admins don't take scheduled runs down with them.

Troubleshooting

  1. Identify who is launching: a human scheduling it, or an ISU triggered by another system.
  2. Check the integration system's security - the launching user's group needs access via the Integration Build/Event domains in the relevant functional area.
  3. For scheduled runs, check the schedule owner - schedules run as their owner, and a deactivated account will break the schedule silently.
  4. Activate pending security policy changes after granting access.
Was this helpful?

Related errors