This seems obvious, and I guess there is a back-end reason it's not already the case. But there are several limitations in airtable that make automation troubleshooting more difficult than it needs to be.
- It would be infinitely more helpful if airtable's failed automation notifications were instant. There's always a delay of at least a few minutes, but often much longer. The delay, combined with the lack of suggestion 2, makes it quite hard to piece together why an automation has failed (usually we are entering data, going back to another job, and seeing an automation failed notification in the emails later) - so it's not that easy to trace the steps back to find out what action triggered the failure.
- Activity log for whole base. Rather than needing to check trash logs, individual record logs, etc, it would be really helpful to have all of this info collated in one space. Ideally this log would also included failed automation runs.
When there are complicated automations that fire other automations, it's sometimes really hard to piece together what actions are creating failures. I often really struggle to recreate failures.
