All Collections
Troubleshooting & FAQs
How to find & screenshot error messages when experiencing an issue in
How to find & screenshot error messages when experiencing an issue in

Locate & screenshot the list of errors happening on the page when you're experiencing a bug in the system

McKenzie avatar
Written by McKenzie
Updated over a week ago

The support team is available to help troubleshoot any issues you may come across while using While we can often find creative solutions to solve problems that arise, we sometimes need help from our development team to get things back in working order.

When there's a bug in the system (rather than a case of user error – we've all been there!) it's often helpful to screenshot the error messages on the page. Follow these steps before taking a screenshot:

❶ Right-click on the page where you're experiencing the error (anywhere within the browser window)

Select Inspect from the dropdown menu that appears:

A pop-up window will appear on the right side of your screen. Across the top, you'll see tabs that read: "Elements, Console, Sources, Network, etc."

Select Console

NOTE: the words you're seeing here (under the red X) are HTML code, not error messages. Select the console tab before taking a screenshot.

Are there any red errors?

If so, please take a screenshot of them. The number of errors is indicated at the top of the window. You may need to scroll up or down the console list to view all the error messages. If that's the case, you may need more than one screenshot.

PLEASE NOTE: The yellow "warnings" are not relevant to any errors you're experiencing, so don't fret if you're unable to capture those in your screenshot. (We won't need them!)

Taking a screenshot


Command+Shift+3 – full screenshot

Command+Shift+4 – cropped screenshot (allows you to take a smaller rectangular screenshot)

You can also use a free app like Monosnap to grab a screenshot.

These screenshots help us pinpoint any system issues or errors a little faster. Thank you so much for your patience while we work to resolve this issue!!

Did this answer your question?