Problem / Background

Currently, the Analytics Dashboard displays the total number of errors and error rates, which is helpful for a high-level overview. However, clicking on these error counts doesn't provide any detailed breakdown of what errors occurred, when they happened, or which scenarios were affected.

As someone who manages many scenarios, I rarely check email notifications for scenario errors. To work around this, I've built an automation using the Notifications API endpoint to forward error alerts to Slack. While this helps, the information available through the Notifications API is still quite limited for effective error monitoring and troubleshooting.

Feature Request

When viewing error counts in the Analytics Dashboard, I would like to be able to drill down into the details, including:

Scenario Name/ID – Which scenario encountered the error

Error Timestamp – When the error occurred (date and time)

Error Type – The type/category of error (e.g., ConnectionError, DataError, RateLimitError)

Error Message – The detailed error description

Execution ID – Link to the specific execution for further investigation

This would allow users to quickly identify and resolve issues without having to navigate through each scenario's execution history individually.

In addition to the dashboard improvements, please expose this error detail data through the API. A dedicated endpoint (e.g., /api/v2/errors or /api/v2/analytics/{organizationId}/errors) that returns:

```json

{

"errors": [

{

"scenarioId": 12345,

"scenarioName": "My Scenario",

"executionId": "abc123",

"errorType": "ConnectionError",

"errorMessage": "Connection refused: target server unavailable",

"timestamp": "2024-12-03T10:30:00.000Z",

"moduleId": 5,

"moduleName": "HTTP Request"

}

]

}

```

This would enable users to:

Build custom monitoring dashboards

Integrate with external alerting systems (Slack, Teams, PagerDuty, etc.)

Perform automated error analysis and reporting

Create proactive maintenance workflows

Use Case

Organizations managing dozens or hundreds of scenarios need efficient ways to monitor errors across their entire Make environment. The current approach requires either checking email notifications (which many users don't monitor closely) or manually reviewing each scenario's execution history—neither of which scales well.

Having error details accessible both in the Dashboard and via API would significantly improve operational visibility and reduce the time needed to identify and resolve issues.