Skip to main content

Sync Status

Sync Status helps you confirm that Development Insights dashboards reflect current data instead of stale metrics. The Sync Status page shows how data collection is progressing for a dashboard. Each row represents one source - a repository, Jira board, or Jenkins job - along with its most recent collection run.

Opening Sync Status​

  1. Open Development Insights from the sidebar and click a dashboard name.
  2. Click View sync status at the top of the dashboard, next to Refresh.
note

View sync status appears only on dashboards tied to specific repositories, boards, or jobs. Cross-provider dashboards such as Engineering Overview do not collect data per source and do not show the link.

Reading the Table​

The table adapts its first column to the dashboard's provider:

ColumnWhat it shows
Repository, Jira Board, or JobThe source being collected. Click the name to open it in the catalog or at the provider.
StatusThe state of the most recent collection run.
Last syncedWhen the run finished, or a dash when it has not completed yet.
ActionsA retry option for runs that did not succeed.

Collection Statuses​

StatusMeaning
CompletedData was collected successfully.
RunningCollection is in progress.
QueuedThe run is waiting to start.
PendingThe source is registered but collection has not started.
FailedAn error stopped the run.
CancelledThe run was cancelled before it finished.

When a run fails, hover over its status to see the error message reported by the collection engine.

Finding a Source​

Use the search box to filter by name, and the filter control to narrow the table to a specific status. You can also sort by name or by last synced time. The table title shows how many sources match your current filters.

Retrying a Failed Run​

Failed and cancelled runs can be collected again without waiting for the next scheduled sync.

  1. Find the row you want to re-run.
  2. Open the actions menu at the end of the row.
  3. Select the retry option.

The status updates as the new run progresses. Retrying requires permission to create Development Insights data; contact your Venue administrator if the option is unavailable.

Troubleshooting​

SituationWhat to do
No sync data appearsNo sources have been collected yet. Import repositories, or add Jira projects and Jenkins jobs, then wait for the first run.
A run stays in PendingCollection has not started yet. Trigger it from the dashboard with Refresh.
A run repeatedly failsCheck the error on the status, then confirm the connection credentials are still valid on the relevant connections page.
The retry option is missingRetry is available only for failed and cancelled runs, and only to users with permission to create Development Insights data.

See Also​