Skip to main content
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:
Opening the Error Reporting tab

Opening the Error Reporting tab

You can filter the incidents by status as well as a date range.
Filtering Web3 Action error reports

Filtering Web3 Action error reports

You can also change the incident status. Besides note-keeping and team collaboration, the status controls failure email notifications: incidents are never resolved automatically, and resolving one means you’ll be emailed again if the same error reoccurs. 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.
Changing the incident status

Changing the incident status

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:
Examining a Web3 Action incident in detail

Examining a Web3 Action incident in detail

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.
Re-running incident executions

Re-running incident executions