Get actionable visibility into event, task, and action errors
Mechanic creates error events when an error occurs during an event run, a task run, or an action run. Each run type has its own error event topic. You can subscribe to these error topics to take action based on these errors (e.g. to send an email letting you know an error has occurred).
There are three error topics that Mechanic can throw: mechanic/errors/action, mechanic/errors/event, mechanic/errors/task.
Subscriptions
Any task may subscribe to error events.
If a task subscribes only to error events, it's qualified to receive all such error events, across all runs in the same Mechanic account.
If a task subscribes to other non-error topics, too, the task will only receive its own mechanic/errors/task and mechanic/errors/action events. It won't be able to receive mechanic/errors/event events.
Topics
mechanic/errors/action
This occurs when an action run encounters an error. (Examples: a server connection failure during an FTP action, or a missing or invalid receipient email address during an Email action.)
This occurs when a task run fails. (Examples: a task run exceeds Mechanic's memory limits, a Liquid parsing or rendering failure, or encountering an error object.)
