Closed ragesoss closed 8 years ago
We should have logging in place now to catch this if it reoccurs. It may be the same root issue as #304.
I don't think the logging is catching the 401 errors. The production.log has many such 401s since we deployed the raven-js capture code earlier this week.
We now have the logging working properly, at least in cases where it doesn't hit the uri limit (which happens on some errors).
Since Friday, we have 13 failed saveTimeline events: http://sentry.ragesoss.com:8080/wiki-ed/production/group/411/
There are three courses among those 13 events:
I vote to close. Any failures will likely be different as a result of the work we've done.
A recent variation of this was closed yesterday with the disabling of delete week
in arrange mode. But yeah, let's close this open something new when we see any additional instances of saveTimeline failure.
For this course, the instructor has been able to make edits to the course description, but attempted edits to the Timeline are not going through; when the instructor returns to the Timeline after leaving, the content has reverted to what originally came out of the wizard.
No edit events from the instructor came through on Sentry for the timeline (unlike edits to course description and adding another instructor). I was able to make successful edits, without issue.
Here is the console log from when the instructor clicks Save on a timeline change: