Overview
Sync History records SIS import and re-sync runs. If you are a Platform Admin or Facilities Manager, you can use it to monitor processing, resume an in-progress run, and review the results of completed or failed runs.
Prerequisites
- SIS Import is enabled for the platform
- You are a Platform Admin or Facilities Manager
Open Sync History
- Open Reservations → SIS Import.
- Review the Sync History table.
- For an in-progress run, select the term to resume it. For a completed or failed run, select View log to open the Import Log.
Sync History shows:
- SIS provider
- Academic term
- Date and time of the run
- User who started the run
- Run status
- Classes created or updated
- Classes or meetings skipped
- Existing reservations overridden
- Classes removed during a re-sync
- Failed records
Understand Run Statuses
| Status | Meaning |
|---|---|
| In Progress | Room Reservations is loading the term, preparing the preview, or importing the classes |
| Awaiting Review | The preview is ready and requires review by a Platform Admin or Facilities Manager |
| Complete | The run finished and its results are available |
| Failed | The run could not finish because of a connection, data, or processing error |
Leaving the wizard does not cancel a run. Open the in-progress term from Sync History to resume the correct step without starting a duplicate run.
Understand Import Counts
Counts can use different units:
- Classes represent the academic classes being imported.
- Reservations represent the individual dates created for those classes.
- People affected represents distinct reservation owners, not the number of rejected reservations.
One class can create many reservations. A term's initial SIS section count can also be higher than the preview count because cancelled, pending, unroomed, or otherwise unusable sections may be excluded.
Review a Per-Run Import Log
- Find the completed or failed run in Sync History.
- Select View log.
- Review the run summary and class-by-class results.
Each result identifies the course, section, room, meeting pattern, term dates, and status. The Import Log shows:
- Classes and reservations created
- Existing SIS classes updated
- Classes skipped because of conflicts
- Classes skipped because their rooms were unmapped
- Classes excluded because they had no usable room or meeting pattern
- Existing reservations overridden
- Imported classes deleted because they were removed from the SIS
- Errors encountered during the run
- The global conflict strategy used
Troubleshooting
A Run Remains In Progress
- Refresh Sync History to confirm its latest status.
- Reopen the run from its term link.
- Large terms can take several minutes to process.
- If the status does not change, contact Concept3D Support with the provider, term, start time, and platform name.
A Run Fails Before the Preview
Possible causes include:
- Expired or invalid provider credentials
- Missing API read permissions
- Firewall rules blocking the Concept3D integration service
- A temporary connection problem with the SIS
- Missing or incomplete class schedule information
If you use Banner, review Prepare Ellucian Banner for the Room Reservations SIS Integration.
Expected Classes Are Missing
Check whether the sections:
- Belong to the selected term
- Are active or closed rather than pending or cancelled
- Have valid meeting dates, days, and times
- Have assigned rooms
- Use rooms that are mapped to Room Reservations spaces
Preview and Completion Counts Differ
Some classes can be skipped during the import because of the selected conflict strategy or unresolved room mappings. Review the completion summary and the per-run Import Log for the reason each class was skipped.
Imported Data Is Incorrect
Correct SIS-controlled information in the SIS, then re-sync the term. Room, date, time, and recurrence cannot be corrected directly on the imported reservation.
Contact Support
When you contact support@concept3d.com, include:
- Institution and Room Reservations platform
- SIS provider
- Academic term
- Approximate run start time
- Current run status
- Screenshot of the error without credentials or API keys
- Example course and section