Kami incident

Schoology 'Open With Kami' buttons not working

Critical Resolved View vendor source →

Kami experienced a critical incident on April 21, 2022 affecting Kami Schoology Integration, lasting 1d 10h. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2022, 02:05 PM UTC
Resolved
Apr 23, 2022, 12:35 AM UTC
Duration
1d 10h
Detected by Pingoru
Apr 21, 2022, 02:05 PM UTC

Affected components

Kami Schoology Integration

Update timeline

  1. investigating Apr 21, 2022, 02:05 PM UTC

    We're getting reports that Kami's Schoology integration isn't working. This appears to be related to our "Open With Kami" buttons not appearing. Our team is investigating the issue. We're sorry for the inconvenience.

  2. identified Apr 21, 2022, 02:43 PM UTC

    We've identified the issue, it's related to a recently Kami Extension update v2.0.15110 we did to fix Kami on Schoology Elementary Mode. To fix this 'Open with Kami' bug we'll need to do a new extension update. The previously released, Kami Extension v2.0.15049 remains unaffected. This doesn't affect assignment creation or our integration to the grader on the teachers side. We've developed a fix, we'll be working as quickly as possible to get it out to everyone, but a Chrome Extension update will probably take up to 24 hours for Google to approve the update. Please look at for Kami Extension v2.0.15112, which contains the fix. WORKAROUND: Please use Kami's share button in the top right corner, and share out a "Anyone with the link" and "Create individual copy". We're sorry about the impact this is causing, and we'll continue to work on ways to minimize the impact.

  3. monitoring Apr 22, 2022, 05:35 AM UTC

    The fixed version v2.0.15112 has now been approved by Google and browsers will automatically update to this version. Thank you for your patience, and our teams will continue to monitor the issue closely to ensure no other issues pop up. Please email us at [email protected] if you have questions, or other issues we can help with.

  4. resolved Apr 23, 2022, 12:35 AM UTC

    This incident has been resolved.