The REST API for transactional monitors does not report 90 or 95 errors (or 0/9095) as errors, they report as a 0 status code to API clients. If a transaction is actually in another error state, this can cause false negatives in monitoring integration, as well as 'flapping' alerts in those integrated systems, due to certain locations intermittently missing a run and reporting as a 0 status code until they run again.
Hi, We are looking into this and will ensure that results are consistently reported regardless of the delivery channel.
