# Past Incidents
Post-mortems on past incidents
# 2020-11-26
Symptom: CloudSkew users encountered an unable to fetch user profile
error and were unable to access their content.
Status: Resolved ✔️
Root Cause: The CloudSkew API was non-responsive and had to be restarted.
Investigation notes:
- Github issue tracking this incident (opens new window).
- Unexpectedly, this API outage did not trigger our automated alerts. This issue now been fixed and the alerts are now triggering normally.
# 2020-11-24
Symptom: New, first-time CloudSkew users encountered an unable to fetch diagram
error when they signed up. Workaround was to just refresh the browser (F5) to make the error go away.
Status: Resolved ✔️
Root Cause: Incident was caused by a race condition where the diagram editor would try to access the new user's profile before it had been created.
Investigation notes:
- Github issue tracking this incident (opens new window).
- Would be nice to refactor the user profile resolution code as a resolve-guard (opens new window) for the diagram editor component.
# 2020-01-28
Symptom: Users experienced errors while printing/exporting diagrams containing custom images.
Status: Resolved ✔️
Root cause: Incident was caused by a misconfigured docker image.
Investigation notes:
- The base image needs to be
mcr.microsoft.com/dotnet/core/aspnet:2.1.15-bionic
. - If we use the regular
2.1
tag instead of2.1.15-bionic
then custom image nodes cannot be printed/exported (some crucial apt-get packages are missing in that tagged image). - The full list of tags can be seen here (opens new window).