As our organization increasingly relies on Make.com, we’ve encountered some challenges, particularly with how errors in scenarios are handled and communicated to our team. Currently, all team members receive email notifications whenever a scenario encounters an error or gets paused. This setup works well initially, but as our team and the number of scenarios grow, some issues occasionally go unnoticed due to two key reasons:

The notification was simply overlooked.

Another team member viewed the notification (via the platform or email) but did not resolve the issue.

When the second case happens, the actual owner of the integration often remains unaware, sometimes for days, that the scenario is paused and not functioning.

To address these issues, I’d like to explore whether the following solutions are possible:

Automated Retry for Paused Scenarios with Errors: Is there a way to create a rule or automation that attempts to reactivate a scenario after it has been paused due to an error?

Persistent Error Notifications: (This is the primary concern) Is it possible to implement a system where, for a scenario paused due to an error but still receiving incoming data, notifications continue to be sent until the issue is resolved?

These functionalities would greatly help us monitor and address issues more efficiently and avoid long downtimes for critical integrations.