Ideas for Apica Synthetic Monitoring

Got an idea? Share it here and we'll have a look at it.

More descriptive browser-level error messages

Two-parter this:

- I had a support ticket 14388 because an error was logged on one of the objects in my journeys. The error was simply 'BAD URI' and I was told that this was that although there was a HTTP200 response on the request there was no HTTP Body so this is what the error meant in this case. Can errors like this have a more descriptive error message?

- For these error messages can you either make it possible to mouseover to get more info or make it clickable and provide a glossary of these messages and what they mean. 




  • Guest
  • Aug 26 2015
  • Sep 18, 2015

    Admin Response

    We will make an effort to improve error messages as much as we can as we see that it can be confusing. I'll leave this as future consideration until we plan this into release.

  • Attach files
  • Guest commented
    September 2, 2015 08:01

    Further example is checkId=51129&resultId=e2bffce3-5c76-476d-9a89-2b3208b1b937

    So it's a 200OK but the error is 'SCRIPT ERROR'...

  • Gravatar
  • Gravatar