Troubleshooting & Error States

Resolving Sync Failures & Expired Tokens

If an integration token expires or a sync fails, LedgeSpace protects the integrity of your reports.

1. The Integration Health Monitor (on your Dashboard) will display a red alert indicating which platform requires re-authentication.
2. During RUSHA AI query execution, the orchestrator performs a health check (getConnectedSources). If a token is expired, it gracefully halts the query and instructs the user to reconnect.
3. To Fix: Navigate to Integrations, locate the flagged platform, and click Reconnect to initiate a fresh OAuth flow.

Troubleshooting Failed Report Deliveries

If a scheduled report fails to deliver:

1. Verify your Custom SMTP Integration settings under Settings > Email Infrastructure.
2. Check that the smtpHost, smtpPort, smtpUser, and smtpPass are perfectly accurate. Ensure no firewall is blocking the connection.
3. Use the Test Connection button.
4. Check your client's email address in their Client Profile for typos, and advise them to check their spam/junk folders if the email sent successfully but was not received.

Handling RUSHA Quota Exhaustion Mid-Cycle

When your monthly "Insights Bucket" is depleted:

1. AI access is immediately restricted to prevent unexpected overage charges.
2. Automated Anomaly Detection and Executive Summary generation will pause.
3. To Resume Instantly: Go to Billing > AI Usage and purchase a Top-Up Block (available in increments of 50 or 120 insights). The AI services will resume the moment the transaction clears.

Maintenance Protocols & Update Triggers

To ensure this documentation remains accurate, the LedgeSpace team strictly adheres to the following update triggers:

• Integrations: Whenever a new platform is added or removed.
• Pricing: Whenever subscription tiers or discounts (e.g., Annual 20% discount) are modified.
• RUSHA AI: Whenever new capabilities or guardrails are implemented. When any of these occur, both these guides and the llms.txt file are immediately updated.