Connections
Review connection health and sync history
Inspect current state, completed runs, and issues before relying on provider data.
Before you start
Who this is for: Users with integration-read access; Sync now requires the corresponding action permission.
- Open the correct connection and organization.
- Know which provider resources or tests you expect the connection to support.
Follow these steps
Inspect the connection identity
Open Connections and choose the intended connection. Check its name, provider, bound account, and lifecycle state. Similar provider names can represent different external accounts, so compare the identity before investigating a missing resource.
Review the latest run
Read the latest run status and available timing information. A requested or starting sync is not a completed collection. Compare run timing with the data you expected to receive, and inspect whether the configured scope includes the relevant resources.
Read activity and issues
Use the connection's history and issue information to understand failures, partial results, or access problems. Read the specific issue and its timing instead of treating a general active label as proof that every resource family collected successfully.
Verify a follow-up run
If authorized and the action is available, choose Sync now after resolving the underlying issue. Wait for a new completed run and inspect its outcome. Then open the relevant test or inventory to check that the expected data appears. If it is still missing, share the connection, run time, and affected view with your administrator.
What you should see
You can identify the connection's current operational evidence and the particular issue or downstream check still needing attention.
If something doesn’t look right
Sync now is absent
Check the connection's allowed actions and your permission. Some lifecycle or setup states do not permit a run.
The connection is active but data is missing
Inspect selected scope, the latest completed run, resource counts, and any setup warnings. Ask the connection administrator whether activation is complete.
Reconnect is requested
Have an authorized administrator use the supported reconnect flow for the same bound account, then verify a subsequent run.
Still need a little help?
Ask the assistant about these steps, or tell our team where you got stuck.
Contact support