Error Messages Guide
📅 Published on: 2025-01-24👤 By: RepoBird Team
RepoBird
AI Development
Error
Messages
No More Guessing
RepoBird's enhanced error system provides clear, categorized error messages that tell you exactly what went wrong and how to fix it.
Complete Error Code Reference
Repository Operations
Errors related to Git repository operations:
| Error Code | Description | Solution |
|---|---|---|
REPO_CLONE_FAILED |
Unable to access the repository | Verify repository exists and you have proper permissions |
REPO_CHECKOUT_FAILED |
Unable to switch to requested branch | Verify the branch name exists and is accessible |
REPO_COMMIT_FAILED |
Unable to save changes to repository | May be due to conflicts or repository restrictions |
REPO_PUSH_FAILED |
Unable to upload changes to remote | Check your permissions and network connection |
REPO_BRANCH_CREATE_FAILED |
Failed to create new branch | Check branch naming conventions and permissions |
REPO_MERGE_CONFLICT |
Merge conflicts detected | Manual resolution needed for conflicting changes |
REPO_PERMISSION_DENIED |
Insufficient repository permissions | Request appropriate access from repository admin |
REPO_NOT_FOUND |
Repository doesn't exist or not accessible | Verify repository URL and access rights |
Pull Request Operations
Errors during PR/MR creation and management:
| Error Code | Description | Solution |
|---|---|---|
PR_CREATE_FAILED |
Unable to create pull request | Check repository settings and permissions |
PR_UPDATE_FAILED |
Unable to update existing PR | Verify PR is still open and accessible |
PR_VALIDATION_FAILED |
PR failed validation checks | Review branch policies and required checks |
PR_DUPLICATE_EXISTS |
Similar PR already exists | Review existing PR before creating new one |
PR_PERMISSION_DENIED |
Insufficient PR permissions | Ensure you have write access to repository |
PR_API_ERROR |
Git provider API error | Check service status or retry later |
Agent Execution
AI agent runtime and processing errors:
| Error Code | Description | Solution |
|---|---|---|
AGENT_TIMEOUT_EXCEEDED |
Run exceeded maximum time limit | Break complex tasks into smaller subtasks |
AGENT_COST_LIMIT_EXCEEDED |
Token/cost limit reached | Simplify issue description or upgrade tier |
AGENT_EXECUTION_FAILED |
Agent failed to complete task | Review conversation viewer for specific errors |
AGENT_INVALID_RESPONSE |
Agent returned unparseable response | Retry or simplify the request |
AGENT_NOT_FOUND |
Specified agent type unavailable | Contact support for agent availability |
AGENT_INIT_FAILED |
Failed to initialize agent | Check configuration and retry |
AGENT_MAX_RETRIES_EXCEEDED |
Failed after maximum retry attempts | Review and clarify issue requirements |
AGENT_NO_CHANGES_MADE |
No code changes were needed | Issue may already be resolved or not actionable |
CLAUDE_PROCESS_EARLY_EXIT |
AI agent stopped unexpectedly | Temporary issue, please retry |
CLAUDE_PROCESS_CRASHED |
AI agent encountered fatal error | Retry the run, our team has been notified |
Security Errors
Security-related issues detected by the AI agent:
| Error Code | Description | Solution |
|---|---|---|
SECURITY_WARNING_DETECTED |
Suspicious code patterns detected | Review task for security best practices |
SECURITY_ERROR_DETECTED |
Malicious code detected, run refused | Remove harmful instructions from task |
Note: Security errors are only visible to admin users. Regular users will not see these errors in the issue run page to prevent exposing security vulnerabilities.
API & Service Errors
External service and API-related issues:
| Error Code | Description | Solution |
|---|---|---|
API_RATE_LIMIT_EXCEEDED |
API rate limit reached | Wait 15-60 minutes for limit reset |
API_AUTH_FAILED |
Authentication failed | Re-authorize GitHub/GitLab App |
API_CONNECTION_ERROR |
Cannot connect to API | Check network and service status |
API_REQUEST_TIMEOUT |
API request timed out | Retry or check service status |
API_INVALID_REQUEST |
Malformed API request | Report issue to support |
API_SERVICE_UNAVAILABLE |
External service down | Wait and retry, check status page |
Configuration Errors
Setup and configuration issues:
| Error Code | Description | Solution |
|---|---|---|
CONFIG_INVALID |
Invalid configuration provided | Review configuration settings |
CONFIG_MISSING |
Required configuration missing | Add missing configuration |
ENV_VAR_MISSING |
Environment variable not set | Contact support for setup help |
General Errors
Miscellaneous error conditions:
| Error Code | Description | Solution |
|---|---|---|
UNKNOWN_ERROR |
Unexpected error occurred | Retry or contact support |
OPERATION_TIMEOUT |
Operation took too long | Retry with simpler request |
PERMISSION_DENIED |
Insufficient permissions | Check access rights |
FILE_NOT_FOUND |
Specified file doesn't exist | Verify file path and name |
IO_ERROR |
Input/output operation failed | Temporary issue, retry |
Where to Find Error Messages
Dashboard UI
- Navigate to Dashboard → Repos → Select repo → Issue Runs
- Click on any failed run to see detailed error information
- Error appears at the top of the run details page
GitHub Comments
- Errors from GitHub-triggered runs appear in @repobirdbot comments
- Clear error code and description directly in the issue/PR
Understanding Error Messages
Each error message includes:
- Error Code - Unique identifier for the issue type
- Description - Human-readable explanation of what went wrong
- Context - Specific details about your run
- Solution - Actionable steps to resolve the issue
Common Solutions
Quick Fixes
- Rate Limits - Wait 15-60 minutes for reset
- Timeouts - Split large tasks into smaller issues
- Permissions - Re-authorize GitHub App in settings
- Merge Conflicts - Update your branch with latest changes
Preventive Measures
- Keep branches updated to avoid conflicts
- Write clear issue descriptions to prevent misinterpretation
- Break down large tasks to avoid timeouts
- Monitor usage to prevent hitting limits
Error Recovery
When you encounter an error:
- Read the error code and description carefully
- Check the conversation viewer for additional context
- Follow the suggested solution steps
- Retry the run after fixing the issue
Getting Help
If you continue experiencing issues:
- Check our status page for outages
- Contact support at support@repobird.ai with:
- Error code
- Run ID
- Repository name
- Steps to reproduce