Coursedog

Submit a Ticket My Tickets
Welcome
Login  Sign up

Common SIS Merge Errors and Resolutions

TABLE OF CONTENTS

Overview

Student Information Systems have many rules and requirements with regards to creating and updating objects. As such, when Coursedog Class Scheduling updates (section data primarily) are merged with the SIS through our integrations, certain requirements must be met in order for data to be accepted. Otherwise, a merge error may occur. 

 

The Coursedog team is committed to documenting all known SIS requirements and sharing those with our partners to ensure best practice set-up of system rules, merge settings, section template settings, etc. in our platform to avoid as many merge issues as possible. 

Best practices

Monitoring your merge error reports regularly (after nightly syncs or once a week during active scheduling) is recommended to catch and resolve these issues. Admins and Super Admins should also have the "View Section Integration Status" permission enabled (under Roles) in order to take advantage of viewing the Integration Errors report in the Reporting console. If you are not utilizing real-time or nightly syncs (and relying on manual POSTs instead), Coursedog recommends you:

  1. Perform regular POSTs throughout the active scheduling cycle to catch any merge errors that may be occurring.
  2. Give your team at least two weeks between the end of scheduling and when POSTs should be finalized in your SIS to resolve any merge errors. 

Resolutions

Some common merge issues may not currently benefit from a configuration prevention or be set up for prevention presently in your instance. Although most are specific to an individual SIS, from time to time the same error applies across multiple SISs. 

Unique to SIS

These are documented, by each available SIS, below. These guides can be downloaded and printed for your convenience.


Multiple SISs

Error in Merge Report



SIS Bandwidth Issues:

During periods of high load, some SIS systems might cause integrations to fail with one of the following errors:


  • 502
  • 504
  • Bad Gateway
  • Connection Timed Out


If these errors are encountered,  it will appear in the merge report:  

Explanation

This error is most commonly due to the SIS closing the connection or failing to accept the connection during periods of high load. If the SIS cannot handle the number of concurrent connections that are being sent, some of the connections may fail as a result. 


How to Resolve

  • If schools experience this during a real-time merge: They should try the real-time merge again to see if the real-time merge succeeds or continues to fail.
  • If schools experience this during the nightly merge: They should attempt to execute a manual merge to see if the merge succeeds or continues to fail.


Recommendations

  • If the school consistently receives the error despite following the appropriate resolution above, they should reach out to customer support.
  • If they are not able to replicate the error, then the error was most likely caused by the SIS during periods of high load and is not an issue on the Coursedog integration side. 


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.