errors / core-connectors / core-connector-task-not-authorized
"The Task Submitted Is Not Authorized" on Integration Launch
The error The task submitted is not authorized for this user. Integration cannot be launched.
What it means
The account trying to launch (or schedule) the integration doesn't have rights to that integration system. Launching an integration is itself 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.
Troubleshooting
- Identify who is launching: a human scheduling it, or an ISU triggered by another system.
- Check the integration system's security: the launching user's group needs access via the Integration Build/Event domains in the relevant functional area.
- For scheduled runs, check the owner of the schedule — schedules run as their owner, and a deactivated owner account breaks the schedule.
- Activate any pending security policy changes after granting.
⚡ Quick fix
Grant the launching user's security group access to the integration event domain for that integration system (then activate pending changes) and re-launch.
✓ Permanent fix
Schedule integrations under a dedicated, never-deactivated service account with documented grants, and include launch-permission checks in the offboarding checklist so departing admins don't take schedules down with them.