Safeguard Docs
Help and Support

Report a bug

Report something broken in Safeguard with steps to reproduce and a recording, and what Safeguard reports on its own when a page fails.

Report a bug

  1. Open the Help & Feedback sheet (the question-mark icon at the top right, or Get Help in your user menu) and select the Bug Report tab.
  2. Choose the Severity: Low, Medium, High or Critical.
  3. Write a Subject that names the problem, and under Steps to Reproduce / Details say what you did, what you expected, and what happened instead.
  4. Optional, and often the quickest way to show it: under Attach evidence, add a Screenshot or a short recording of the problem. See Attach a screenshot or recording.
  5. Select Send.

The sheet shows Your ticket reference. The report then appears in Messages › Support, where you follow it, reply and rate the answer like any other request (how).

What Safeguard adds to your report

So that the team can reproduce the problem, the report carries, for the Safeguard team only:

  • the page you were on, without its query string;
  • your workspace's tenant, organization and product identifiers;
  • your browser's user-agent string;
  • the version of the Safeguard app you were using.

When a page fails on its own

When something fails in the app, such as a screen that crashes, a script error or a request to Safeguard that fails, the app reports the failure to Safeguard's engineering team by itself. You don't need to do anything, and you don't get a ticket or an email for it.

The report carries no personal data: no page content, request bodies, headers, cookies, tokens, query strings, email addresses or names. It holds the error message with personal details removed, the start of the technical trace, the app version, the browser and operating system family and, for a failed request, its method, status and a path template such as /projects/:id. The same failure is reported at most once every five minutes.

If the error screen shows an Error ID, include it when you report the problem: it lets the team find that exact failure.

On this page