Skip to main content
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

1

Open the connection.

Open the connection under Integrations.
2

Confirm the account.

Confirm the provider account and team.
3

Review status and permissions.

4

Reconnect if offered.

If Flow offers Reconnect, authorize the provider again.
5

Test the connection.

Run a live automation test only after the connection is ready.
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

1

Open the source.

Open the source in the matching area.
2

Review the source card.

Review Connected, Indexed, and Sync on the source card.
3

Open source actions.

Open the source actions menu.
4

Sync now.

Use Sync now once when it is available.
5

Reconnect if expired.

Reconnect the source if Flow says authorization expired.
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. If the problem continues, report the connection or source name, team, last successful time, and visible error through Feedback.

​
Repair ticket sync

1

Open the source.

Open Integrations, filter to Ticketing, and open the affected connection. Choose its Ticketing tab, then select the source.
2

Review readiness.

Review readiness, provider status, and scope.
3

Review mapping tabs.

Review the Field mappings, Status mappings, and Priority mappings tabs.
4

Wait out delays.

If the source is delayed or throttled, wait for the next retry before changing configuration.
5

Reconnect if expired.

Reconnect when Flow reports expired authorization.
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 for permissions, limitations, and recovery steps.

​
Repair a ticket that imported with the wrong values

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.