# Sign-in, uploads, and issue submission

Canonical: https://fairleadhq.com/docs/recorder/troubleshooting-connections/

Updated: 2026-10-07
Publication state: published
Product version: Source verified — 52de40a

Agent summary: Resolve account and destination failures without duplicating work. A timeout can leave an issue command outcome unknown; check the tracker before retrying.

## Prerequisites

- A connected-project workflow and its error message

## Inputs

- The failing sign-in or submission operation

## Outputs

- A targeted recovery action without duplicate submission

## Limitations

- A timeout can leave an issue command outcome unknown; check the tracker before retrying

## Permissions

- Project access and authorization for the failing destination

## Privacy

- Review content and destination before sharing


Resolve account and destination failures without duplicating work.

Read the failing operation before retrying. Sign-in, tracker commands, attachments, and report storage have separate outcomes.

## No project profile is available

Ask your Fairlead administrator to assign a project profile to your account. Signing in successfully does not establish project access or configure a destination.

## Sign-in expired or a token failed

Use **Connect via browser** again. For a one-time connection token, obtain a new token if it expired or was already used. Browser restart can require reconnecting. Confirm the selected project afterward.

## Tracker credentials are missing

Follow Recorder's Control Plane link to connect the personal account required by the project. For Azure DevOps, the link may open the project's Issue Tracker page for the selected organisation. Reconnect expired or revoked authorization there.

Do not paste provider tokens into Recorder.

## The destination is not configured

A missing tracker route or Data Plane endpoint is an administrator configuration issue. Ask your administrator to check the selected project and destination. Personal sign-in alone cannot repair it.

If report storage is disabled by project policy, upload and enhancement remain unavailable even when the tracker works.

## A version compatibility error appears

An unsupported protocol error means the extension and Bridge service cannot complete that operation together. Update Recorder through your normal Chrome update process or ask your administrator to align the service. Repeating the same command will not fix the mismatch.

## Submission timed out

A timeout, including a 504 response, can mean the issue command's outcome is unknown. Check the tracker for the issue or update before retrying. Keep the time and project reference for investigation.

## Only part of the submission succeeded

Preserve the successful issue reference. Retry a failed screenshot attachment independently when offered, and resolve storage failure separately. Report upload failure does not undo issue creation. For description conflicts, review the append/replace choice in [Create or update an issue](https://fairleadhq.com/docs/recorder/issue-trackers/).