Kami incident

Kami not saving changes on fillable PDF text boxes and not rendering images on a document

Major Resolved View vendor source →

Kami experienced a major incident on January 12, 2022 affecting Kami Frontend, lasting 41m. The incident has been resolved; the full update timeline is below.

Started
Jan 12, 2022, 06:33 PM UTC
Resolved
Jan 12, 2022, 07:15 PM UTC
Duration
41m
Detected by Pingoru
Jan 12, 2022, 06:33 PM UTC

Affected components

Kami Frontend

Update timeline

  1. identified Jan 12, 2022, 06:33 PM UTC

    We've identified two separate issues with a new release of Kami where 1) New changes to pre-made fillable text boxes are not triggering a "save" and causing our users to lose work on those fillable boxes. The workaround is to use our Kami "text tool" instead and type into the Kami textbox to save that work. 2) Images from the original document are not rendering, so the pages appear blank. There are no current workarounds. Our engineers are actively working on fixes for both cases. If you have an issue unrelated to these two issues, please email us at [email protected] so that we can investigate further. We're sorry for the disruption caused by these bugs, we hope to automatically roll out an update to fix them soon.

  2. resolved Jan 12, 2022, 07:15 PM UTC

    We've rolled out a fix for both issues. To get the update, please refresh Kami, and the app will then automatically download the update. It should automatically refresh the Kami page again once it's updated. We're actively monitoring for any new issues. Please email us at [email protected] if you're encountering another problem. Sorry again for the disruption this has caused. Edit: We've discovered another issue where the Turn In button dropdown will say "We couldn't load this assignment. Please refresh and try again". This bug has been fixed as part of the latest update.