> ## 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 connections and sync

> Repair connected accounts and source sync problems.

Automation connections are managed under **Integrations**. Knowledge sources are
also under **Integrations**, filtered to knowledge integrations. Asset sources are
also under **Integrations**, on the connection's **Assets** tab. Ticket sync is
also under **Integrations**, filtered to **Ticketing**.

## Repair a connection

<Steps>
  <Step title="Open the connection.">
    Open the connection under **Integrations**.
  </Step>

  <Step title="Confirm the account.">
    Confirm the provider account and team.
  </Step>

  <Step title="Review status and permissions." />

  <Step title="Reconnect if offered.">
    If Flow offers **Reconnect**, authorize the provider again.
  </Step>

  <Step title="Test the connection.">
    Run a live automation test only after the connection is ready.
  </Step>
</Steps>

Ask a team Manager or organization administrator if you cannot reconnect it. Do not create a second
connection to work around an unclear error.

## Repair a source sync

| Source type | Open |
| - | - |
| Knowledge | **Integrations** |
| Assets | **Integrations** (the connection's **Assets** tab) |

<Steps>
  <Step title="Open the source.">
    Open the source in the matching area.
  </Step>

  <Step title="Review the source card.">
    Review **Connected**, **Indexed**, and **Sync** on the source card.
  </Step>

  <Step title="Open source actions.">
    Open the source actions menu.
  </Step>

  <Step title="Sync now.">
    Use **Sync now** once when it is available.
  </Step>

  <Step title="Reconnect if expired.">
    Reconnect the source if Flow says authorization expired.
  </Step>
</Steps>

Provider changes can take time to appear. Check the latest sync time before running another sync.

If files are indexed but the source says **Not synced yet**, run the first tracked sync before
relying on freshness. If no sync action is available, include that state in **Feedback**.

If a ServiceNow Knowledge source shows **ServiceNow count mismatch**, the sync completed. Flow
indexed the articles ServiceNow returned. See
[ServiceNow Knowledge Base](/integrations/knowledge/servicenow-kb#troubleshooting).

If the problem continues, report the connection or source name, team, last successful time, and
visible error through **Feedback**.

## Repair ticket sync

<Steps>
  <Step title="Open the source.">
    Open **Integrations**, filter to **Ticketing**, and open the affected connection.
    Choose its **Ticketing** tab, then select the source.
  </Step>

  <Step title="Review readiness.">
    Review readiness, provider status, and scope.
  </Step>

  <Step title="Review mapping tabs.">
    Review the **Field mappings**, **Status mappings**, and **Priority mappings** tabs.
  </Step>

  <Step title="Wait out delays.">
    If the source is delayed or throttled, wait for the next retry before changing configuration.
  </Step>

  <Step title="Reconnect if expired.">
    Reconnect when Flow reports expired authorization.
  </Step>
</Steps>

If the problem continues, include the source, team, latest successful poll, and visible error in
**Feedback**.

## Repair ServiceNow custom-table verification

If Flow cannot read ServiceNow metadata, choose one path:

* Grant the integration user read-only access to `sys_db_object`, `sys_dictionary`, and `sys_choice`, then run automatic discovery again. This is the recommended path.
* Ask an organization administrator to choose **Configure manually**, enter the complete mapping, match one readable test record with the source filter, and choose **Test table access**.

Manual verification does not prove that the table formally descends from Task. It verifies only that Flow can read one matching row with the configured runtime fields. An empty result is not enough: add a safe matching test record or correct the filter. A table proven not to descend from Task cannot use the manual path.

After manual verification, Flow labels the source as manually verified. Change the table or a mapped runtime field only when you can test the table again. A later denial from the optional automatic metadata refresh does not block an unchanged, valid manual source.

See [ServiceNow ticketing custom-table setup](/integrations/ticketing/servicenow#set-up-a-custom-table) for permissions, limitations, and recovery steps.

## Repair a ticket that imported with the wrong values

| Symptom | Where to fix it |
| - | - |
| Wrong Flow state | Add the provider status value under the right Flow state on **Status mappings** |
| Priority did not change on a linked ticket | Add the provider priority value on **Priority mappings**. Existing tickets keep their current Flow priority |
| Flow writes the wrong provider value back | Set the outbound default for that Flow state or priority |
| Subject or description arrives with markup or trailing spaces | Add a text cleanup change on **Field mappings** |
| Wrong person as requester | Check the **Requester** and **Opened by** rows on **Field mappings** |

Use **Mapping preview** on the source to test a sample provider Title, Status, and Priority before
you rely on the change. Preview does not save mappings or create tickets. Tickets that already
imported keep their current values, so open one and re-sync its provider record after you fix a
mapping.

## Related topics

* [Jira Service Management](/integrations/ticketing/jira-service-management)
* [ServiceNow ticketing](/integrations/ticketing/servicenow)


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