Sync and dataset messages
Home and first-time setup
Section titled “Home and first-time setup”Home could not load
Section titled “Home could not load”Fix: Select Retry, or reload the page. You are still signed in.
Setup needs another role
Section titled “Setup needs another role”Cause: Brightspace setup is not finished, and your role cannot do the next step. Fix: Ask for help finishing setup or changing your role. See Roles and permissions.
If you don’t see this menu or button, your role doesn’t include it. Ask someone who can edit roles (Owners and Admins by default).
No datasets found
Section titled “No datasets found”Full message: Please verify your OAuth credentials have the correct permissions for Brightspace Data Sets. (or a specific reason from Brightspace).
Cause: The scan found no datasets you can sync. Usually the service user lacks Can Access
Brightspace Data Sets, or the app lacks the scope datasets:bds:read. Fix: Correct it in
Brightspace, then select Retry scan, or Update connection settings.
The first sync did not complete
Section titled “The first sync did not complete”Also shown as Recover the first sync or, for roles that cannot sync, The first sync needs recovery.
Cause: The first sync failed or stopped. The reason and the failed datasets are shown. Fix: Correct the cause (see the sync failure messages below), then select Retry first sync. Ask for help if that button is unavailable.
Start the first sync
Section titled “Start the first sync”Cause: Datasets are chosen but the first sync has not run. Fix: Select Start first sync.
Some data did not refresh
Section titled “Some data did not refresh”Full message: N datasets failed. Reports that depend on unavailable data may be incomplete. or The latest sync completed with warnings. Reports continue to use the available data.
Fix: Open Sync details on Home or Sync history to see which datasets failed and why, fix the cause, and sync again.
Data is out of date
Section titled “Data is out of date”Full message: The last successful sync is N days old. Reports still use the most recent available data.
Fix: Run a sync on Data > Sync. On a paid plan, check Sync history for failing automatic syncs.
Welcome to Rowseta! Your data is syncing.
Section titled “Welcome to Rowseta! Your data is syncing.”Cause: Your first sync is running. Fix: Nothing to do; wait for it to finish.
Starting and running syncs
Section titled “Starting and running syncs”Brightspace is not connected. Configure credentials to enable syncing.
Section titled “Brightspace is not connected. Configure credentials to enable syncing.”Also shown on Datasets as Brightspace not connected.
Fix: Select Configure credentials and connect Brightspace.
Unable to start sync. Please try again or check your Brightspace connection settings.
Section titled “Unable to start sync. Please try again or check your Brightspace connection settings.”Fix: Try again. If it keeps failing, test the connection on Integrations > Brightspace.
Sync already running
Section titled “Sync already running”Fix: Wait for the current sync to finish, or stop it.
No datasets to sync
Section titled “No datasets to sync”Fix: Enable at least one dataset on Data > Datasets.
Unable to stop sync. Please try again.
Section titled “Unable to stop sync. Please try again.”Fix: Select Stop again.
Sync stopped. Completed datasets have been saved.
Section titled “Sync stopped. Completed datasets have been saved.”Cause: You stopped the sync. Fix: Nothing to fix. Run Sync now when you are ready.
New data is available from Brightspace.
Section titled “New data is available from Brightspace.”Fix: Select Sync now.
We couldn’t start the sync workers. No data was changed.
Section titled “We couldn’t start the sync workers. No data was changed.”Fix: Try again. Contact support if it persists.
Sync failures
Section titled “Sync failures”Last sync failed. The Brightspace connection needs attention.
Section titled “Last sync failed. The Brightspace connection needs attention.”Also on Home: The Brightspace connection needs attention. Sync history labels it Connection or Auth.
Cause: Brightspace refused Rowseta’s sign-in. Fix: Select Fix connection or Details and follow the steps; see the next entries.
Brightspace rejected Rowseta’s secure sign-in because the Rowseta registration in Brightspace points to the wrong key location.
Section titled “Brightspace rejected Rowseta’s secure sign-in because the Rowseta registration in Brightspace points to the wrong key location.”Also shown in the Fix the Brightspace connection dialog: Brightspace rejected our secure sign-in. Its Rowseta registration points to the wrong JWKS URL in the Rowseta OAuth 2.0 app.
Fix:
- Copy the correct URL from the dialog (It should be). It is your Rowseta address followed by
/.well-known/jwks.json. - In Brightspace, open Manage Extensibility, then the OAuth 2.0 tab, and select the Rowseta app (your institution may have renamed it).
- Paste the URL into its JWKS URL field and save.
- Back in Rowseta, select Test connection, then sync again.
If the test says Brightspace still rejected the sign-in. Check that the OAuth 2.0 app’s JWKS URL was saved, then test again., check the saved value in Brightspace.
Brightspace rejected Rowseta’s secure sign-in: it could not find our current key
Section titled “Brightspace rejected Rowseta’s secure sign-in: it could not find our current key”Also: …it could not verify our key. This usually means the Rowseta registration in Brightspace was changed or re-created.
Fix: Open the Rowseta registration in Brightspace and save it again without changes; this refreshes Brightspace’s copy of the key. Then sync again. Contact support if it continues.
Could not authenticate with Brightspace. Check your BDS credentials in Settings.
Section titled “Could not authenticate with Brightspace. Check your BDS credentials in Settings.”Also: Unable to authenticate with Brightspace. Check your OAuth credentials in Settings.
Fix: Check the OAuth 2.0 app and Client ID on Integrations > Brightspace.
Brightspace download limit reached. Resets in …
Section titled “Brightspace download limit reached. Resets in …”Also: Brightspace download quota exceeded. The sync will automatically retry when the quota resets. Shown as Download limit reached on the progress panel and Quota in Sync history.
Cause: Brightspace limits how much can be downloaded in a period. Fix: Wait for the time shown, then sync again.
Last sync failed on our side. Your Brightspace setup is fine.
Section titled “Last sync failed on our side. Your Brightspace setup is fine.”Also: Data storage configuration error. Contact support., We couldn’t store your synced data… and We couldn’t read your Brightspace connection settings…. Sync history labels it Storage.
Fix: Try again later. Contact support if it persists; nothing needs changing in Brightspace.
Brightspace rejected the data download. This usually resolves on retry.
Section titled “Brightspace rejected the data download. This usually resolves on retry.”Also: Failed to download data from Brightspace. This dataset will be retried automatically. and Unable to reach Brightspace. The LMS may be temporarily unavailable.
Fix: Wait and sync again. Rowseta retries failed datasets automatically.
This dataset failed to sync. It will be retried automatically.
Section titled “This dataset failed to sync. It will be retried automatically.”Also: Failed to process the downloaded data. This dataset will be retried automatically. and …retried automatically in N minutes.
Fix: Nothing to do; Rowseta retries. If it keeps failing, check Sync history for the reason.
This dataset was synced from a snapshot created N days ago but recent daily updates could not be applied.
Section titled “This dataset was synced from a snapshot created N days ago but recent daily updates could not be applied.”Shown as Stale data in Sync history.
Fix: Run a sync again to apply the missing updates.
Data sync failed unexpectedly. Contact support.
Section titled “Data sync failed unexpectedly. Contact support.”Also: Last sync failed., The sync did not complete.
Fix: Select Details for the reason, try again, and contact support if it persists.
You’ve used all of your manual syncs.
Section titled “You’ve used all of your manual syncs.”Also: No manual syncs remaining. Your data will not refresh until you upgrade., no sync credits remaining, Upgrade for unlimited syncs, No manual syncs remain.
Cause: Your Organization has used every Evaluation manual sync. Your data stays available. Fix: See Billing.
Use a manual sync?
Section titled “Use a manual sync?”Also: This is your last credit. After this sync, your data will stop refreshing until you upgrade.
Fix: Select Use credit & sync to continue, or Cancel.
Email: Data sync failed: dataset name
Section titled “Email: Data sync failed: dataset name”Cause: A dataset failed during a sync. The email repeats the reason. Fix: Look up the reason on this page.
Email: BDS schema changes detected
Section titled “Email: BDS schema changes detected”Cause: Brightspace added or removed columns in a dataset. New columns are added automatically; removed columns are no longer available. Fix: Check reports that use removed columns.
Sync history
Section titled “Sync history”No sync history yet
Section titled “No sync history yet”Fix: Run a sync on Data > Sync.
Completed with warnings / Partial / Failed / Skipped
Section titled “Completed with warnings / Partial / Failed / Skipped”Cause: Some datasets in that sync had warnings, failed, or were skipped. Fix: Select the row to see each dataset’s reason, fix it, and sync again.
Datasets
Section titled “Datasets”Scan failed.
Section titled “Scan failed.”Also: Couldn’t reach Brightspace. Check your OAuth credentials on the Brightspace page.
Fix: Test the connection on Integrations > Brightspace, then select Scan Brightspace again.
Scan already running. Check progress below.
Section titled “Scan already running. Check progress below.”Fix: Wait for the scan to finish.
Your last scan was N days ago.
Section titled “Your last scan was N days ago.”Fix: Select Scan Brightspace to check for new datasets.
A sync is in progress. Dataset changes are disabled until it completes.
Section titled “A sync is in progress. Dataset changes are disabled until it completes.”Also: cannot delete datasets while a sync is running.
Fix: Wait for the sync to finish, then make your change.
Failed to enable datasets / Failed to disable datasets
Section titled “Failed to enable datasets / Failed to disable datasets”Also: Failed to enable N datasets, Failed to disable N datasets.
Fix: Make sure no sync is running, then try again.
Cannot disable required dataset
Section titled “Cannot disable required dataset”Cause: Users, Course Access and Course Access Log are always synced. Fix: Leave them on.
Failed to delete dataset data / Failed to delete datasets
Section titled “Failed to delete dataset data / Failed to delete datasets”Fix: Try again. You cannot delete data during a sync.
Delete … data? / Delete all dataset data?
Section titled “Delete … data? / Delete all dataset data?”Cause: Deleting permanently removes synced data and its sync history. Fix: Confirm only if
you mean it. For Delete all data, type delete.
Role Details dataset has not been synced yet
Section titled “Role Details dataset has not been synced yet”Fix: Enable Role Details on Data > Datasets and sync.
Organizational units data not available. Sync the Organizational Units dataset first.
Section titled “Organizational units data not available. Sync the Organizational Units dataset first.”Fix: Enable Organizational Units on Data > Datasets and sync.