> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testorim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to get help, and what to send so we can actually fix it.

## Getting in touch

<CardGroup cols={2}>
  <Card title="Email" icon="mail" href="mailto:info@fulgic.com">
    [info@fulgic.com](mailto:info@fulgic.com)
  </Card>

  <Card title="Report a bug from the app" icon="bug" href="https://app.testorim.com">
    The bug icon in the dashboard navigation opens a form that captures the
    context for us.
  </Card>
</CardGroup>

The in-app report is the better option when something went wrong in a run. It
attaches the page you were on, the latest run id, the build versions, your
viewport and the timestamp automatically, so you only have to describe what you
expected.

## What to include

For a run that behaved wrongly, the **run id** is worth more than a paragraph
of description. From it we can see every step, every screenshot, the state read
off each element, and the console and network activity.

Then, in one or two sentences:

* what you expected
* what happened instead
* whether the screenshot agrees with the report

<Note>
  If a report **blamed your site and the screenshot disagrees**, that is a
  defect in Testorim and we treat it as one. Send the run id.
</Note>

## Before you write

Most issues have a named cause on the failed step. Worth two minutes first:

<CardGroup cols={2}>
  <Card title="Debugging a failed run" icon="search" href="/test-execution/debugging">
    Read the cause, then the evidence.
  </Card>

  <Card title="Common issues" icon="circle-help" href="/troubleshooting/common-issues">
    Refusals, logins, addresses, seats.
  </Card>

  <Card title="Browser failures" icon="monitor-x" href="/troubleshooting/browser-failures">
    Error statuses, dialogs, downloads, timeouts.
  </Card>

  <Card title="Reliability" icon="activity" href="/troubleshooting/reliability">
    Why a test is flaky and what to change.
  </Card>
</CardGroup>

## Sharing a run with someone outside your workspace

Use a share link from the run page. It is revocable, can be given an expiry,
and the page it serves has credentials, environment headers, browser storage
state and console/network detail stripped.

## Security

If you believe you have found a security issue, email
[info@fulgic.com](mailto:info@fulgic.com) with the details and please do not
open it anywhere public first.

## Legal

[Terms](https://app.testorim.com/terms) · [Privacy](https://app.testorim.com/privacy)


## Related topics

- [Common issues](/troubleshooting/common-issues.md)
- [List a project's saved procedures](/api-reference/procedures/list-a-projects-saved-procedures.md)
- [Get one procedure by id](/api-reference/procedures/get-one-procedure-by-id.md)