Browser issues get messy when the support request is vague.

"It broke" is not enough. A useful evidence package should show what the user did, what the browser saw, what the application returned, and what is safe to share.

The Minimum Evidence Package

Start with the basics:

  • Issue summary.
  • Exact reproduction steps.
  • Timestamp and timezone.
  • Browser name and version.
  • Operating system.
  • Affected account, tenant, or workspace when safe.
  • Screenshot of the visible error.
  • Ticket number or case ID.

This gives support a timeline and context before they open any files.

When to Add a HAR File

Add a HAR file when network evidence matters.

Examples:

  • Login or SSO failures.
  • Redirect loops.
  • API requests failing in the browser.
  • Assets not loading.
  • CORS errors.
  • Slow page loads.
  • Tenant-specific browser behavior.

Ask the customer to start the capture before reproducing the issue, clear old network entries, enable Preserve log when navigation matters, and review the file before sharing.

When to Add Console Logs

Add console logs when browser-side behavior matters.

Examples:

  • Blank screen.
  • JavaScript error.
  • UI button does nothing.
  • Runtime warning.
  • Extension conflict.
  • Error appears after the page has already loaded.

Console logs can contain sensitive data too. Review them before upload.

When to Add Screenshots

Screenshots are best for visible state.

Use them for:

  • Error banners.
  • Broken layouts.
  • Incorrect values.
  • Disabled controls.
  • Missing UI.
  • Reproduction proof.

Crop or redact unrelated data before sharing.

Privacy Review Checklist

Before evidence leaves the customer or internal team, check for:

  • Cookies.
  • Authorization headers.
  • API keys.
  • Passwords.
  • Emails.
  • Customer names.
  • Account IDs.
  • Internal notes.
  • Query parameters.
  • Browser tabs and bookmarks.
  • Screenshots with private data.

If the customer cannot safely review the files, ask whether a screenshot, timestamp, or server-side log correlation can replace the artifact.

Copyable Intake Template

Could you send a browser troubleshooting package for this issue?

Please include:
- What you expected to happen.
- What happened instead.
- Exact reproduction steps.
- Timestamp and timezone.
- Browser and operating system.
- Screenshot of the visible error.
- HAR file if the workflow makes a network request.
- Console log if the page shows a JavaScript error or blank screen.

Please review or sanitize files before uploading them through the secure link in this ticket.

FAQ

Should every browser issue include a HAR file?

No. Ask for a HAR only when network evidence matters. Screenshots or console logs may be enough for visual or client-side issues.

What makes evidence hard to use?

Missing timestamps, incomplete reproduction steps, over-redacted files, unrelated browsing activity, and files shared without context.

Should customers email HAR files?

Usually no. Use a secure upload path and follow your team's data-handling policy.

What if the evidence contains sensitive data?

Mask or remove the sensitive values when possible. If the sensitive value is needed, ask exactly what field is required and share the minimum through an approved path.

CTA

Redaction Retriever helps teams gather HAR files, console logs, screenshots, and notes into a local workspace before exporting a support-ready bundle.