AzentAzent

Troubleshooting & Common Issues

The agent doesn't respond to my comment

  • •Make sure you @mentioned the correct bot user name (check Configuration > Current User)
  • •Verify the project is enabled in the Dashboard (Projects page)
  • •Confirm you are a member of the allowed group (default: Contributors)
  • •Check that your subscription is active and you haven't exceeded agent hour limits
  • •Verify the PAT hasn't expired — go to Configuration and click Test Connection

Test Connection fails

  • •The PAT may have expired — create a new one in Azure DevOps and update the configuration
  • •The PAT may not have the required scopes — see Azure DevOps Connection
  • •The organization name may be incorrect — verify it matches your Azure DevOps URL

Enabling a project fails to register webhooks

  • •The bot user must be a member of the Project Administrators group in that project — Azure DevOps requires this role to create service hook subscriptions
  • •Confirm the bot user has at least Basic access level in the organization
  • •Re-run Test Connection after fixing permissions, then toggle the project off and on again

Run stays in Queued status

  • •You may have reached your concurrent runs limit — wait for a running job to finish or upgrade your plan

Run fails with an error

  • •Check the run details in the Dashboard for the error message
  • •Common causes: AI provider API key is invalid or has insufficient quota, PAT doesn't have required permissions, repository is too large to clone within the timeout
  • •The default agent timeout is 3 hours — very large tasks may exceed this

Agent produces incorrect code

  • •Add a validation pipeline to catch build/test failures
  • •Create custom skills to teach the agent your project's patterns and conventions
  • •Add a preprompt in .azent.json with project-specific context
  • •Be more specific in your work item descriptions and trigger comments
  • •For complex features, break down the work into smaller tasks

Self-hosted deployment fails

  • •Ensure you have Owner or Contributor role on the Azure subscription
  • •Check that az and jq are installed and up to date
  • •Verify the license token is valid and not expired
  • •Check that the Azure region supports all required resource types (Container Apps, Cosmos DB serverless)
  • •Review the Bicep deployment output for specific error messages