The Revenue Recovery platform communicates important information through various types of error messages and notifications. Understanding these messages and knowing how to respond helps you quickly resolve issues and maintain productive workflows. These guides provide comprehensive error documentation organized by type and feature area, along with systematic troubleshooting approaches for common scenarios.

What These Guides Cover

The error message documentation helps you identify, understand, and resolve issues by covering:

• Error type identification - Understanding HTTP status codes, error landing pages, toast notifications, and application-specific messages
• Detailed error catalogs - Comprehensive listings of specific errors with causes and resolutions
• Feature-specific troubleshooting - Resolving errors related to EHR connections, authentication, data processing, and exports
• Integrated troubleshooting patterns - Systematic diagnostic approaches embedded within application-specific error documentation
• Escalation guidance - Knowing when to self-resolve, contact your administrator, or reach out to Ailevate support
• Deployment model considerations - Understanding which errors apply to SaaS vs. on-premise environments
• Best practices - Preventing common errors and optimizing platform reliability

Types of Error Messages

The platform uses several methods to communicate errors and status information:

Error Severity Levels

• 🟢 Green - Success confirmations (auto-dismiss after 5-10 seconds)
• 🟡 Yellow/Blue - Warnings and informational messages
• 🔴 Red - Errors requiring attention (manual dismissal required)
• 🚨 5xx Server Errors - Platform-level issues requiring immediate support contact

Error Documentation Guides

HTTP Status Codes and Landing Pages

Industry-standard response codes (4xx client errors, 5xx server errors) and full-page error displays that indicate request outcomes. Detailed coverage of common codes like 400, 401, 403, 404, 500, and 503 with specific causes and resolution steps. Includes error landing pages for authentication failures, permission errors, and resource access issues.

Use this guide when: You see error codes in browser consoles, network monitoring tools, or encounter full-screen error messages preventing page access.

Toast Notifications

Temporary messages in the top-right corner providing immediate feedback on actions. Comprehensive catalog of success confirmations, warnings, and error alerts with visual examples and troubleshooting guidance.

Use this guide when: You see colored notification popups after performing actions like saving settings, testing connections, or exporting data.

Application-Specific Errors

Errors specific to Revenue Recovery features like EHR connections, data synchronization, user management, and exports. Organized by feature area with deployment model considerations (SaaS vs. On-Premise) and integrated troubleshooting patterns for systematic diagnosis and resolution.

Use this guide when: You encounter issues with specific platform features like EHR connectivity, claim processing, authentication, or report generation, or when you need systematic diagnostic approaches for complex scenarios.

Quick Start: How to Use These Guides

Follow this process when encountering an error:

1. Identify the error type - Note whether it's a toast notification, error page, HTTP status code, or feature-specific message
2. Navigate to the relevant guide - Use the links above to access detailed documentation
3. Follow the troubleshooting steps - Each guide provides systematic resolution procedures
4. Check deployment model notes - Some errors have different causes or resolutions for SaaS vs. On-Premise deployments
5. Escalate if needed - Use the guidance below to determine when to contact your administrator or Ailevate support

When to Self-Resolve vs. Escalate

Self-Resolve

You can typically troubleshoot on your own when:

• Error messages provide clear resolution steps in these guides
• Issues relate to configuration you control (user roles, security settings, form inputs)
• Validation errors or data formatting issues occur
• HTTP 4xx client errors appear (400-499 range)

Contact Your Administrator

Contact your organization administrator when:

• User roles or permissions need changes
• Security policies require adjustment (IP Allow List, Trusted Domains, session timeout)
• Account unlocking or organization membership changes are needed
• Configuration changes exceed your authority level

Contact Ailevate Support

Contact [email protected] when:

• HTTP 5xx server errors occur (500-599 range) - Always contact support for server errors
• Persistent errors remain after following all troubleshooting steps
• Feature behavior doesn't match documentation
• EHR connection issues persist after verifying credentials and network connectivity
• Platform-wide issues affect multiple users or organizations

💡 Pro Tip: Most errors are temporary or configuration-related. Working through the troubleshooting steps in these guides often leads to quick resolution and builds your confidence in managing the platform independently.

Error Guide Sequence

For comprehensive error troubleshooting, we recommend this guide sequence:

1. HTTP Status Codes and Landing Pages - Start here if you see numeric error codes (400, 403, 404, 500, 503) or encounter full-page error messages
2. Toast Notifications - Review if you see colored notification popups
3. Application-Specific Errors - Dive deep into feature-specific issues with integrated troubleshooting patterns for complex scenarios

Need Help?

If you encounter issues while troubleshooting:

• Search for the specific error message in the appropriate guide using the sequence above
• Review the integrated troubleshooting patterns in Application-Specific Errors
• For infrastructure-level diagnostics and system health monitoring, see System Monitoring & Health and Component Diagnostics & Troubleshooting
• Contact your organization administrator for permission, role, or security policy questions
• Email [email protected] for platform-level issues or when troubleshooting steps don't resolve the problem

📘

Infrastructure vs. Application Errors
This guide covers user-facing application errors (HTTP codes, toast notifications, feature-specific messages). For infrastructure-level monitoring (Relay services, Elasticsearch cluster health, AI Warehouse hardware diagnostics), see the System Monitoring & Health guide for monitoring strategies or Component Diagnostics & Troubleshooting for hands-on diagnostic commands.