Skip to main content
Resolve common automation issues with these troubleshooting steps. For additional support, contact your Ona account manager.

​
Debugging failed executions

When an automation fails:
  1. Navigate to the automation details page
  2. Click on the failed execution
  3. Review the Action conversation for error messages and execution details
  4. Check which step failed and review the error output
  5. Contact your Ona account manager with the execution details for assistance
The Action conversation shows the complete execution log, including commands run, outputs, and any errors encountered.

​
Trigger issues

​
Manual triggers not starting

Issue: Automation doesn’t start when triggered manually Solutions:
  1. Verify your user account or service account has access to the target repositories or projects
  2. Check that the repositories match your search query
  3. Ensure the project exists and contains repositories
  4. Verify you have permissions to run automations in your organization
Learn more about project access and sharing.

​
Pull request triggers not firing

Issue: Automation doesn’t run when pull requests are opened or updated Solutions:
  1. Verify the webhook is correctly configured in GitHub or GitLab
  2. Check the webhook configuration matches the details from the automation settings
  3. Confirm the webhook secret is entered correctly
  4. Verify the webhook is active and not disabled
  5. Check that pull request events are selected in the webhook configuration
See Pull Request Triggers for webhook setup instructions.

​
Time-based triggers not running

Issue: Scheduled automation doesn’t execute at the expected time Solutions:
  1. Verify the schedule is configured correctly (remember schedules run on UTC)
  2. Check that the automation is not paused or disabled
  3. Confirm your service account has access to target repositories
  4. Review the automation execution history for any error messages
See Time-based Triggers for schedule configuration.

​
Git and repository access issues

Issue: Automation fails with “repository not found” or “access denied” errors Solutions: For user accounts:
  1. Verify you have access to the target repositories in your SCM (GitHub/GitLab)
  2. Check that your personal access token has the required scopes
  3. Ensure the repositories haven’t been moved or deleted
For service accounts:
  1. Verify the service account has Git authentication configured
  2. Check the personal access token is still valid and hasn’t expired
  3. Confirm the token has required permissions (repo, read:user, user:email, workflow)
  4. Ensure the service account has access to the target repositories
Learn more about Service Accounts and Git authentication setup.

​
Permission errors

Issue: “Permission denied” or “Insufficient permissions” errors Current limitation: Projects must be enabled for “all members of an organization” for automations to access them. Solutions:
  1. Navigate to the project settings
  2. Ensure the project is shared with “all members” of your organization
  3. Verify your service account is a member of the organization
  4. Check that the automation’s service account has the necessary SCM permissions
This limitation will be addressed in a future update with more granular access controls. Learn more about project sharing and organization management.

​
Getting help

If you continue to experience issues after trying these solutions:
  1. Gather the following information:
    • Automation name and ID
    • Execution ID (if available)
    • Error messages from the Action conversation
    • Steps to reproduce the issue
  2. Contact your Ona account manager with these details
Enterprise customers can also reach out to their account representative for dedicated support.

​
Next steps