Overview
In Student Success & Engagement, the data integration has two major steps:
- The Connect2/Accelerate process
- The Import process
See the SIS Data Import Process for a visual on each of these steps.
This quick guide outlines what successful data transfer looks like, as well as the types of errors or failures that can occur at each step. Use this in conjunction with Quick Guide: View JSON Extract and Imported Data, Quick Guide: SIS Integration Troubleshooting, and Quick Guide: Data Integration Changes to understand many common SIS Integration issues.
Connect2/Accelerate
Success
If the Connect job completes successfully, the JSON data will be visible in SS&E Administration and can be accessed from SIS Integration > Datafeeds > Download Extract.
Failure
Issues with the Connect job (scheduled task) processing some or all feeds can often be identified in External Logging. Navigate to SS&E Administration > Advanced > External Logging (https://{yourinstitution}.avisoapp.com/aviso/logMessage/list). If External Logging is not working, try downloading the Connect2 Full Log from the External Logging screen.
Feed Failure
- Feed failures can be identified when there is an entry in the External Logging with an error.
- Search for the feed name or select Log level ERROR
- Click into the error message for more detail on the specific error.
- If you notice an individual feed with errors, generally it can be solved with changes to the source data or by updating the Accelerate query.
Task Failure
- Task failures can be identified when the Connect2 Task does not start at all or when it does not finish.
- Search for “SIS IMPORT” to confirm that the Connect2 Task is starting and finishing on schedule (typically runs 4x per day).
- If you notice that there are no log entries for a specific day/time period, begin by troubleshooting the scheduled task and the Connect Server.
See SIS Integration Troubleshooting: Connect2/Accelerate for basic troubleshooting instructions.
Import
Success
If the SIS Import job completes successfully, the SIS data is available in SS&E and visible from SS&E Administration > SIS Integration > Datafeeds > Imported Data View (allows Administrator users to view data in the SS&E database).
Failure
Import Process Failure
In some cases an unexpected issue can arise that causes the entire import process to fail. To see this type of error:
- Navigate to SS&E Administration > Advanced > Batch Processing > and switch to page 2
- Click the sisImportBatchJob link
- You will be able to view the run time and status of previous and currently running import jobs. A status of "FAILED" or "STOPPING" means the import process failed. You can dig deeper by looking into the job log, but it's generally recommended to reach out to support for assistance if you notice consistent job failures.
Data Feed File Failure
If a data feed JSON file is invalid this can cause the entire file to fail to parse. To see this type of error:
- Navigate to SS&E Administration > SIS Integration > Import Errors
- Search for "parse" in the "Search Message Text" field.
- This type of failure is most common if there are unexpected fields in the data feed JSON file. Review the SIS Import Definitions article and the troubleshooting article: SIS Import Error "Could not parse file:"
Record Import Failure
If certain records in the import data feed fail, in most cases, record import errors can be searched.
- Navigate to SS&E Administration > SIS Integration > Import Errors
- Import errors are often "expected" if the JSON files include records that reference missing data from other feeds. More information about data feeds associations can be found in the SIS Import Definitions article.
Caching Issue
If the data is correct in the JSON file, but incorrect in the Imported Data View and there are no Import Errors, there could be a caching issue. To resolve a caching issue:
- From SS&E Administration, navigate to SIS Integration > Manual API Calls
- Enter the data stream name(s) that you wish to reset in the Connector Cache box.
- Select Reset Cache.
Note: it is not recommended to reset all caches as the following import will take a very long time. - Review the data after the import runs again to confirm the issue is resolved.
See SIS Integration Troubleshooting: Import for basic troubleshooting instructions.
Additional Information
- Quick Guide: View JSON Extract and Imported Data
- Quick Guide: SIS Integration Troubleshooting
- Quick Guide: Data Integration Changes
- SIS Data Import Process
- Data Stream Out of Date Troubleshooting
- SIS Integration Troubleshooting Guide
- Run Accelerate Queries Locally on the Connect Server
- Accelerate Configuration