SEE ALSO:
- Troubleshooting
- Problem: Entities in work hierarchy are orphaned and belong to different scopes of work
- How to collect a HAR file for troubleshooting UI issues
- No Cards are displayed
- Cannot Prioritize Cards on a View
- Project and Team selection is reset
- Troubleshooting Performance Issues with On Demand Accounts
- No Lanes are displayed
Brief summary of this article:
When something is not working, it is always helpful to see the full error details, and not just Oops... Something's wrong or BadRequest
Checking Network
To check the error, you can open Ctrl+Shift+j and navigate to the Networks tab and try to reproduce the error.
Failed requests will be highlighted in red.
Click on this failed request and go to the Response tab
Once you have “ErrorId”, kindly share that with our Support team
You can also add verbose=1 to the URL and pull the full error message directly from the response:
Mind the placement of verbose=1 - it has to be after ? and before #
Checking Browser Console
To check the error, you can open Ctrl+Shift+j and navigate to the Console tab and try to reproduce the error.
The failed request will be highlighted in red
The stack trace can be very helpful here - it can give you the name of the file which is failing. You can click on the link to be taken to the exact place where JS is failing:
Verbose usage on API calls
Verbose plays a major role in getting a detailed error message which helps in understanding the error much better.
Here is the difference in the error message without and with verbose in the URL.
Without verbose in URL:
With verbose in URL:
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.