Error Reporting

When your Web3 Action fails, the failure is recorded as an Incident. Incidents group failures by Action version and error: the first occurrence of an error creates a new incident, and repeated occurrences of the same error are added to it. You can access incidents in the Actions section in the main navigation tree, through the sub-tab Error Reporting: You can filter the incidents by status as well as a date range.

​

Incident statuses

An incident has one of three statuses. Besides note-keeping and team collaboration, the status controls failure email notifications:

• Ongoing - the status an incident is created with. Repeated occurrences of the same error are grouped under the incident and don’t trigger additional emails.
• Acknowledged - marks the incident as seen. Emails for the incident’s error stay muted, same as Ongoing.
• Resolved - closes the incident and re-arms notifications: if the same error occurs again, a new incident is created and you receive a new email.

Incidents are never resolved automatically, even if later executions succeed. When you open a specific incident, you will see each and every instance of your Action executing with all the info about how the execution went. You can also explore a detailed view for each of the incidents, and see the execution status, errors, payload, and logs for each individual execution of your Actions: If you would like to test changes to your Action configuration through Execution History and see how changes to your Action would impact its previous executions, you can rerun single, multiple, or all of the incidents at any point.