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

# Troubleshoot conversations and requests

> Recover a missing conversation, unavailable reply, or attachment problem.

## A conversation is missing

<Steps>
  <Step title="Check filters.">
    Check the selected team and current filters.
  </Step>

  <Step title="Search for it.">
    Search by conversation number, requester, or title.
  </Step>

  <Step title="Clear hiding filters.">
    Clear filters that may hide resolved or differently assigned work.
  </Step>

  <Step title="Confirm team access.">
    Confirm that you still have access to the team.
  </Step>
</Steps>

## You cannot reply

Read the message below the reply area.

| Message or state | What to do |
| - | - |
| View-only access | Ask a team Manager to grant you an Agent role or higher. |
| No requester reply channels | Add a **Work note** and ask a team Manager to check the channel. |
| Email reply failed | Ask a team Manager to open **Settings → Flow Teams**, expand the team, and check **Flow settings → Email**. |
| Slack reply failed | Ask an organization administrator to verify **Settings → Chat**. |
| Reply is still sending | Refresh once and check the thread before trying again. |

If the message is still not in the requester thread after refreshing, send it again once. A
**Work note** is team-only and does not notify the requester.

The same rule applies to apparently stuck assignment, status, or work-note changes: refresh and
check **Recent activity** before repeating the action.

## A browser chat file needs attention

| Status | What to do |
| - | - |
| **Checking** | Wait for Flow to finish checking the file. |
| **Ready to send** | The file is ready. Other files can still need attention. |
| **Upload interrupted** | Select **Send** again. Files marked **Ready to send** are not uploaded again. |
| A specific failure reason | Read its tooltip, then remove or replace that file as instructed. |

Flow does not send a browser chat message while one of its selected files still needs attention.
The draft, ready files, and failed files stay in the composer so you can retry or remove only the
affected file. See [Request tracking](/setup/request-tracking#browser-chat-file-support) for
the supported formats and browser limits.

## A request attachment is unavailable

| Status | What to do |
| - | - |
| **Scanning** | Wait for the security check to finish before downloading the file. |
| **Quarantined** | The security check flagged the file as unsafe. Ask the sender for a safe replacement. |
| **Failed** | The upload or security check did not complete. Ask the sender to upload the file again. |
| **Blocked by upload policy** | Read the reason shown with the attachment. A policy can block the file even after it uploads. |

If the issue continues, report it through **Feedback** with the conversation number and visible
status.

## Related topics

* [Request tracking](/setup/request-tracking)
* [Troubleshooting](/setup/troubleshooting)
* [Support](/setup/support)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.