Exalate Troubleshooting Section
New Exalate includes a dedicated Troubleshooting section that displays errors preventing synchronization. The unified console shows recent errors with timestamps, error types, affected connections, and specific failure messages like "Outgoing script error: Cannot get property value on null object, Error line 18". This centralized error view makes it significantly easier to identify sync problems compared to checking separate consoles in Exalate Classic.
Aida AI Diagnosis for Errors
Aida AI provides intelligent diagnosis when errors occur, explaining issues in easy-to-digest language with context-aware suggestions for resolution. When you encounter a script-related error, Aida analyzes it and explains it. You can view the full analysis and receive guidance on fixing the problem directly within the troubleshooting interface.
Common Reasons for Sync Failures
Common reasons for sync failures include:
- script execution errors
- trigger configuration issues
- or missing field mappings
The error list categorizes problems by type such as "Outgoing script error," "Script execution failure," "Network," and "TrackerResetException," helping you quickly identify whether the issue stems from your configuration or system connectivity. Each error entry shows which connection and specific nodes are affected, making it easy to pinpoint where to focus your troubleshooting efforts.