Real-time information about each synchronization can be found in the status page that would typically exists within your primary working portal. Below you can see an example of a Status table on connect.bentley.com.
Typically here, you can see the status for each related synchronization job. As well as access the Synchronization Report.
Image 1 - Synchronization status report example
Status information
This provides a quick overview of whether the synchronization is ongoing or has encountered issues. Synchronization typically would have one of these statuses:
| In queue | Files or data have been selected for synchronization, but the synchronization process has yet to start. Job is waiting in a queue until the synchronization of the previous file is completed, or a synchronization service will be prepared to process those. |
| Starting | The process to synchronize your files or data has been initiated. |
| In progress | Synchronizing your files or data is actively taking place. That includes processing source data from its location and synchronizing new changes to an iModel. |
| Success | The process of synchronizing your files to iModel has been completed. It means that all files have been synchronized without errors. NOTE: successfully synchronized files can have warning and information messages that can impact how data was processed and what got synchronized. We recommend reviewing the synchronization report for any issues that may occur during synchronization. |
| Success with issues | The process of synchronizing your files to iModel has been completed, but critical synchronization errors that can impact what data is being synchronized to the model have been identified. We recommend reviewing the synchronization report for any issues that may occur during synchronization. |
| Partially succeeded | Some file synchronization to iModel has been completed, but at least one file synchronization has failed. |
| Failed | Synchronizing your files to iModel was unsuccessful, and an issue or error occurred. |
| Skipped | The synchronization process for specific files was intentionally bypassed because the source file(s) have not been modified since the previous synchronization completion. |
Details information
Synchronization details information provides a comprehensive view of what occurred during the synchronization process.
- All files have failed
- Access to Data Source Denied
- Failed to access the data source
- Failed to orchestrate file processing retry
- File is Protected
- Document Not Found
- Another User is Pushing
- Connector Lock Errors
- Datasource Authentication Type Is Not Supported
- Drawing File With Wrong Config
- Failed to process the file
- File processing was canceled
- Geodetic coordinate system not supported
- iModel Access was Forbidden
- Unmap Input File
- User is not authenticated
- Unrecognized Format
- Schema Upgrade Failure
- Source file is not accessible
- iModel Access was Forbidden
- Source file not found at location
- Source file pre-authenticated URL is expired
- iModel Not Found
- Connector lock error
- Workset override not found for Open Building Designer files
Additional properties
- Duration information - describes how much time it took to synchronize files to Model.
- Start Time information - refers to the timestamp of when a synchronization process was started.
- End time information - refers to the timestamp of when a synchronization process was completed.
- Type information - describes how synchronization is being initiated:
- Manual means that synchronization has been started manually and will not be automatically repeated in the future.
- Schedule means the data synchronization process occurs according to a specified job schedule. In scheduled synchronization, data is synchronized automatically without requiring manual initiation each time. The schedule will be inactivated if the scheduled job fails five times in a row. The synchronization job must be started manually after blocking issues are resolved. Learn more in the Suspending synchronization section.
Suspending synchronization
Connections scheduled synchronizations will be suspended after 5 consecutive failures. To restore the recurrence, manual synchronization needs to be triggered. That could be done by:
- the connection owner;
- any team member who has Modify iModel permission for that iModel.