Synchronize data and inspect history
Refresh connected records and distinguish accepted work from completed synchronization.
A connector-sync workflow pulls records from a connected source into Strive. Run it on demand when you need fresh data, or manage its schedule in Workflows. The connection provides access; the workflow controls the synchronization process.
Follow a refresh
Open the relevant workflow and start the intended run. A queued or accepted result confirms that the request was recorded. Wait for the run's final status and inspect its results before assuming the source is fully refreshed.
Where source activity is displayed with the connection, it lists recent sync attempts with their time, trigger, and status. Successful runs can summarize new, updated, and unchanged records. Those counts describe the run's treatment of records, rather than the total number of items that exist at the provider.
Interpret statuses
Running means work is still active. Succeeded means the sync completed according to its run contract. Failed indicates an execution failure and should be investigated with its error. Queue unavailable distinguishes a dispatch problem from a provider-side processing failure.
A successful sync can legitimately produce no new records if the source was unchanged or the configured selection had no matches. Compare the new, updated, and unchanged counts with the filters and source scope.
Recover deliberately
If access expired, reconnect and test the connection first. If the run failed in a workflow step, inspect that step's configuration. Starting repeated runs without correcting the cause can create noisy history without improving freshness.
After recovery, open the relevant Data source and inspect representative records and provenance. A connection test, a successful sync status, and the expected output content answer separate questions.