Syncs and sync history
Start your first sync
Section titled “Start your first sync”If your Evaluation Organization has zero free syncs left and no completed sync, confirming your dataset selection saves it without starting a sync. A price check runs instead, and the Your price card appears. Follow the price check and purchase steps. After purchase, the first sync is a full sync.
When free syncs are available, after choosing datasets, select Start first sync. Data Sync shows Queued, Downloading, Processing and Saving; Home shows First sync in progress.
While the first sync runs, select View sync progress on Home or open Data > Sync in the sidebar. Both require permission to access analytics and manage syncs (analytics.access and analytics.manage_sync). The progress panel can show Preparing sync while Rowseta checks for updates across your datasets. You can close the page and return later; the sync continues in the background.
At Your data is ready, select Build your first report. If Home says The first sync did not complete, check Recover the first sync, correct the cause and select Retry first sync.
The first-sync completion email has the subject Your first Brightspace sync is complete. It goes to active people with the built-in Owner or Admin role, rather than to billing contacts.
Run a later sync
Section titled “Run a later sync”In Data > Sync, select Sync now. In Evaluation, confirm Use a manual sync? with Use credit & sync. If some datasets fail but one completes, Completed with warnings uses one manual sync. If all fail, no manual sync is used. A manual sync that finds nothing new to load doesn’t use one of your syncs. With none left, reports stop refreshing. LMS Account count checks use none and do not refresh reports.
A sync that finds no new data usually finishes in about a minute, though timing varies. It keeps cached report results rather than clearing them. When data changes, report caches are cleared so later runs use the refreshed data.
The page shows Data freshness, Datasets, Total records and, on paid plans, Auto-sync. Stop ends a running sync; completed datasets remain saved. While the stop request is being sent and while the sync is stopping, the panel shows Stopping, and Stop and Sync now are disabled. When Rowseta itself is ending an interrupted sync, the panel can instead show Finishing up. Some data didn’t load this time. Stop and Sync now stay disabled while it finishes. When it ends as stopped, the status line shows the stop outcome or Stopped. If the request fails, the controls show Unable to stop the sync. Please try again. Before downloading starts, Stop can end the sync at once as stopped, but if it is still being set up it may take time to end; no manual sync is used when that sync ends as stopped without downloading anything. A second Stop after it has ended says This sync has already ended. Last synced counts only Completed syncs, including Completed with warnings, not stopped or failed syncs.
Recover a failed or partial sync
Section titled “Recover a failed or partial sync”When a sync fails, Rowseta retries automatically up to three times: the first retry is about 5 minutes after the failure, the second about 15 minutes after the next failure, and the third about 45 minutes after that failure. Automatic retries do not use your Evaluation manual sync allowance. A sync someone stopped is not retried. Brightspace sign-in or registration problems are not retried either; correct the connection before syncing again.
The overall failure email, Data sync failed, goes to active people with the built-in Owner or Admin role only after the third retry fails. For Brightspace sign-in or registration problems, it is sent at once without a retry. A separate dataset failure notice can still arrive at once with the subject Data sync failed: followed by the dataset name. That notice does not wait for the automatic retries.
After an overall failure email, the next successful sync triggers one recovery email, Your Rowseta syncs are working again, to the operational recipients. A dataset failure notice alone does not trigger this recovery email.
Open Details or Sync history for failures. After a full load, failed daily updates show in Sync history as Completed with warnings. The full snapshot stays available to reports. The warning says The full snapshot is available, but recent daily updates could not be applied. The missing daily updates will be retried automatically. Other warnings show the snapshot’s age and days behind. For dataset completeness messages and automatic repair, see Missing daily updates.
After retries are exhausted: The full snapshot is available, but recent daily updates could not be applied after automatic retries. Check details, correct the cause and sync again. Contact support for persistent failures.
If a dataset failure starts with read existing data failed, dataset left unchanged:, the text after the colon describes the cause. The dataset stays unchanged. Check the cause, correct it and sync again; contact support if it persists. If the cause includes existing data not found for a previously synced dataset; run a full sync, use Re-import all under More sync actions to run a full sync.
During dataset replacement, a report can show This data is being updated. Try again in a few minutes.
If Report a problem appears on a Failed or Completed with warnings sync in Sync history, select it. Sync details attach automatically; describe the problem.
If Fix connection appears, open it and compare the Brightspace app’s JWKS URL with It should be. Select Open Brightspace connection, then test and save before syncing. Check the service user, Client ID and datasets:bds:read scope. See Data connection.
For download limits, wait for Brightspace’s reset time; for rejected downloads, retry later. Contact support for persistent failures.
Data set changes
Section titled “Data set changes”Each sync detects changes to data set columns. Data set schema change emails go to active people with the built-in Owner or Admin role. After the sync, Rowseta checks saved reports and flags those that use removed columns with the report warning. When a report is first flagged, those same operational recipients get an email naming the report, quoting the warning and linking to it. That email is handled separately from the warning: Rowseta retries a temporary delivery failure automatically a limited number of times, and the report keeps its warning either way. Being the report’s owner or a billing contact alone does not make someone a recipient. The warning clears when a later post-sync check finds the saved query compatible.
Brightspace data freshness
Section titled “Brightspace data freshness”When a date can be confirmed, reports show Brightspace data as of <date and time>; the widget details page shows Data as of: followed by the date. This is Brightspace’s extract date; reports show the oldest dataset date. Brightspace publishes daily; Rowseta adds each update.
In reports, after 48 hours, the line turns amber: The latest update hasn’t arrived yet. If you can open Data syncs, you see Sync (and a reason only when Evaluation has no manual syncs left or the last sync failed). Otherwise, ask someone. The tooltip’s Help with Syncs opens this section.
Missing daily updates
Section titled “Missing daily updates”When Rowseta cannot yet confirm that a dataset holds every daily update, its status can show Missing daily updates. Reports that use it say Some data is missing recent daily updates, so this may not be current. When no date can be confirmed, the date line says Data date not confirmed yet. Course widgets and widget details show the same warning sentence; widget details can also show Data date not confirmed yet. when no date is confirmed.
Rowseta repairs the dataset automatically during later syncs, applying the missing daily updates or downloading its full data again when needed. The message clears once Rowseta confirms the dataset is complete. If it stays after several syncs, check Sync history and contact support.
After this update, each dataset that is still selected for sync needs a fresh full download the next time a sync includes it, so that sync can take longer than usual. Datasets that are turned off are not downloaded.
Re-import or delete all data
Section titled “Re-import or delete all data”On Data Sync, open More sync actions beside Sync now. Re-import all downloads enabled datasets again.
Select Re-import all to open Re-import all?. The dialog says: “Re-import all reloads every dataset from Brightspace and can take a while.” In Evaluation, it adds: “This will use 1 of your N remaining manual syncs.” N is the number remaining. Select Re-import all to start or Cancel to close without starting. The menu item is disabled while a sync is running or stopping, when Brightspace is not connected, or in Evaluation when the manual sync count has not loaded or none remain.
If you can manage datasets, select Delete all data. Wait for any running sync to finish first. The dialog lists every report, saved draft and insight widget in your Organization that uses synced data, with its owner and a link when you can open it. Edit or remove these first; they block deletion. Reports that Rowseta could not check also count as using the data. Built-in reports are listed but do not block deletion; they show no data until the next sync.
When nothing blocks deletion, type delete and select Delete all data to confirm. The dialog says: “This permanently deletes all synced data. Reports stop showing it right away, and the stored files are removed within about a day. Discovery records and sync history are kept.”
Dataset selection is kept too. Deleting does not switch datasets off. The dialog warns about enabled optional datasets returning on the next sync and tells you to switch them off on the Datasets page first; switched-off optional datasets have no return warning. Required datasets, Users, Course Access, Course Access Log and Organizational Units, cannot be switched off and return on the next sync.
Results opened before deletion stop working. Run the report again; export requests from those old results are refused after deletion.
Check sync history
Section titled “Check sync history”Open Data > Sync history for times, Type, Trigger, datasets, volume, duration and status. Select a row for each dataset’s records, warnings and errors.
