Debugging failed executions
- Open the failed execution from the automation details page
- Review the Action conversation for error messages
- Check which step failed and review output
Trigger issues
Manual triggers not starting
- Verify account has access to target repositories/projects
- Check repositories match your search query
- Verify permissions to run automations
Pull request triggers not firing
- Verify webhook configured correctly in GitHub/GitLab
- Check webhook secret matches automation settings
- Confirm PR events are selected in webhook config
Time-based triggers not running
- Verify schedule is correct (schedules run on UTC)
- Check automation isn’t paused or disabled
- Confirm service account has repository access
Repository access errors
“Repository not found” or “access denied”:| Account type | Check |
|---|---|
| User | SCM access? PAT scopes? Repo still exists? |
| Service account | Git auth configured? PAT valid? Required scopes? |
Permission errors
“Permission denied” or “Insufficient permissions”:- Projects must be shared with “all members” for automations to access them
- Verify service account is organization member with SCM permissions
Sharing issues
Can’t see Automations page
- Verify organization has automations enabled
- If not admin, confirm you’re in a group with shared automation access
”Project not found” on shared automation
The automation targets a project you don’t have access to. Ask admin to share the project, or select a different target.Git auth errors on shared automations
Shared automations run under your identity. Re-authenticate at app.ona.com → Settings → Git Providers.Can’t see other users’ executions
Expected - Executors only see their own executions. Admins see all.Getting help
Contact your Ona account manager with:- Automation name/ID and execution ID
- Error messages from Action conversation
- Steps to reproduce