If something in Tripleseat isn't working as expected and our team can't reproduce it on our end, we may ask you for a browser trace, also called a HAR file. This is most helpful for pages that load slowly, time out, don't finish loading, or show errors that only happen on your device or browser.
What is a browser trace?
A browser trace is a recording of everything your browser loads from Tripleseat while you use it, and how long each piece takes to load. It's saved as a HAR file (a file ending in .har) that you can attach to your support ticket.
How it helps us troubleshoot
- It shows the exact requests that happen when the issue occurs, and how long each one takes.
- It shows errors that don't appear on your screen.
- It helps us see whether the issue is coming from Tripleseat or from something on your side, like your network, a firewall, or a browser extension blocking part of the page.
- It gives our Development team the details they need if a fix is required.
Before you start
- Log in to Tripleseat before you start recording. This keeps your login details out of the file.
- Go to the page right before where the issue happens, so the recording only includes the steps that show the issue.
Please note: A HAR file can include information from the pages you visit while recording. Only record the steps needed to show the issue.
For Chrome:
- Open Google Chrome and log in to Tripleseat.
- Go to the page right before where the issue happens.
- Click the three dots on the top right-hand corner of your screen > click "More tools" > click "Developer tools." You can also press F12 (Windows) or Command + Option + I (Mac).
- Click the "Network" tab.
- Check the box for "Preserve log."
- Click the clear button (a circle with a line through it) to clear anything already listed.
- Make sure the record button on the top left of the panel is red. If it's gray, click it to start recording.
- Reproduce the issue in Tripleseat.
- Click the download arrow at the top of the Network tab > select "Export HAR (sanitized)" and save the file.
For Firefox:
- Open Firefox and log in to Tripleseat.
- Go to the page right before where the issue happens.
- Click the three lines on the top right-hand corner > click "More tools" > click "Web Developer Tools." You can also press F12 (Windows) or Command + Option + I (Mac).
- Click the "Network" tab.
- Click the gear icon on the right-hand side of the Network tab > select "Persist Logs."
- Click the trash can icon to clear anything already listed.
- Reproduce the issue in Tripleseat.
- Click the gear icon again > select "Save All As HAR" and save the file.
For Safari:
- Open Safari.
- Click "Safari" on the top left-hand side of your screen > select "Settings" (called "Preferences" in older versions).
- Click "Advanced," then check the box for "Show features for web developers" (called "Show Develop menu in menu bar" in older versions).
- Log in to Tripleseat and go to the page right before where the issue happens.
- Click "Develop" in the menu bar > select "Show Web Inspector." You can also press Command + Option + I.
- Click the "Network" tab.
- Check the box for "Preserve Log."
- Click the trash can icon to clear anything already listed.
- Reproduce the issue in Tripleseat.
- Click "Export" at the top of the Network tab and save the file.
For Edge:
- Open Microsoft Edge and log in to Tripleseat.
- Go to the page right before where the issue happens.
- Click the three dots on the top right-hand corner > click "More tools" > click "Developer tools." You can also press F12.
- Click the "Network" tab. If you don't see it, click the "+" button and select "Network."
- Check the box for "Preserve log."
- Click the clear button (a circle with a line through it) to clear anything already listed.
- Make sure the record button on the top left of the panel is red. If it's gray, click it to start recording.
- Reproduce the issue in Tripleseat.
- Click the download arrow at the top of the Network tab > select "Export HAR (sanitized)" and save the file. If you don't see the download arrow, make the Developer tools window wider.
Sending us the file
- Reply to your support ticket and attach the .har file. If the file is too large to attach, compress it into a .zip file first.
- In your reply, let us know:
- The page you were on and what you clicked
- About what time the issue happened
- What you expected to happen
A short screen recording of the issue is also helpful if you're able to include one.
Once we have the file, our team will review it and follow up on your ticket with what we find.