Vous êtes sur la page 1sur 1

Using F12 for Troubleshooting

Note: These steps are applicable to Edge and I.E. Using other browsers, you will find similar functionality
and the steps should translate close enough to provide the session data needed to help troubleshoot.
F12 Developer tools provides a great way to see what might be causing issues with the site you are
trying to use. Please use the following steps to investigate. Once the problem page is loaded you can
SAVE which will generate a file that our engineering team can use to help diagnose the issue. Below are
the steps to use F12.

1. Log in to your account and Navigate to your starting page which might be your dashboard or the
place you started when the issue occurred
2. Start F12 making sure your function keys are enabled (FN on most keyboards)
3. Set up your session by making sure the F12 tool Network TAB and Console Tab are clean to start
a. Always refresh from server is a toggle switch with on and off states. When on, Microsoft
Edge downloads all page elements from the remote server, not from the browser cache.
b. Clear cache removes saved files from the browser's cache. Browsers commonly save
page elements to disk and use them again for faster reloads. When you're trying to get
the true measure of a page's load time, clearing the cache makes sure all elements are
being downloaded from the network.
c. Clear cookies ensures that all cookies related to the current domain are removed, so
that you get the experience of loading the page for the first time.
d. Clear entries on navigate is a toggle switch with on and off states. When in the off state,
network traffic for a window or tab is recorded continuously as the browser moves from
page to page. When in the on state, recorded traffic is cleared each time you navigate to
a new page. This is turned on by default. Toggle to OFF to ensure navigation is

SAVE creates a .HAR file

4. Now you are ready to start navigating to reproduce the issue. Click on the Green Arrow to start
recording the session.
5. Navigate to the problem page or if you are already on the page you can refresh the page using
the refresh button on your browser.
6. Continue navigating till you get to the issue.
7. Check for console errors and check the network tab for errors. Once the target page is loaded or
you see the problem manifest completely you can click on the red stop button.
8. Capture and provide the results to MVA Support
a. Screenshot from the console tab, and any error indicators on the site page
b. The best way to provide a good view of your session is to SAVE. Clicking on the SAVE
icon next to the square STOP button will generate a .HAR file and you will be prompted
to save on your computer. Tip: When you provide content please be sure to specify the
date and time so can see if the issue correlates to any known issues that we are seeing
on the platform or on the network.