Resolved -
Although we have not heard any official messages from Schoology, it appears that the API issues have been resolved on their end. Sync have resumed.
Dec 23, 05:14 UTC
Update -
Error rates have dropped again and we are begging to resume syncs. Last word from Powerschool is that they are "looking into it" (as of last Friday).
Dec 22, 15:37 UTC
Update -
...and we're back to seeing elevated error rates again after a relatively smooth morning and early afternoon.
Dec 17, 22:21 UTC
Update -
Everything appears to be back to normal, we're waiting on a few more districts to sync.
Dec 17, 16:53 UTC
Monitoring -
We have noticed some API requests begin to succeed again. We are not sure if this is temporary (or if it applies to 100% of API requests) but we are monitoring the situation.
Dec 17, 01:10 UTC
Update -
The issue with the Schoology API has been escalated to "major". At this point, it appears that close to 100% of API requests to Schoology are failing. This includes SSO, syncs, coursework, and grade requests.
We are temporarily pausing all Schoology syncs in order to free up queue space for other sources.
Dec 16, 14:56 UTC
Identified -
We have a deployed an update to our roster sync code to try to workaround this ongoing issue. This should help roster data begin to flow again. This change does not impact the assignments, grades, and coursework APIs, so you may still experience random, intermittent 403 errors from Schoology.
Dec 11, 21:14 UTC
Investigating -
We are currently investigating reports of an unusual number of School API errors. This may affect any Schoology integrations, including ones where you are only accessing class roster data via Edlink. We are receiving random (intermittent) 403 errors from AWS Cloudfront (Schoology's CDN provider). These errors do not actually correlate to permissions issues in Schoology as they appear to be random and will succeed after several retries or a significant time delay.
Our system, by default, replays external requests up to 5 times, but they are in relatively short succession so this retry logic does not provide a workaround in this situation.
Roster data is all still available (the Edlink API itself still returns data as usual), but Edlink may not receive subsequent roster updates from Schoology during this time.
We are attempting to work with Schoology to help them determine the root cause.
Dec 9, 17:41 UTC