Today all errors are categorized as ‘Errors’ or ‘Critical’ (Critical is only when the page is disconnected or blocked, as far as I know.
There are some errors that are categorized as ‘Errors’ that should not be ‘Errors’.
For example, failed JSON Mapping.
With more AI + Integrations we’re using External Requests more and more, and failed JSON Mappings are, in most cases, by design, and not an error at all.
With all JSON Mappings categorized as errors, it becomes difficult/impossible to find true critical errors.
I suggest:
- Re-categorizing JSON Mapping errors to ‘Warning’ or Info’ level
- Ability to filter Critical/Error/Warning/Info messages
- Keep ‘Error’ category for true errors (5xx, 4xx, invalid content, etc). Basically errors that we cannot catch in our automations using conditions/user fields.
- Bonus points: ability to filter by type of error.
