Detecting Content Changes in Scroll Sites Does Not Work

Incident Report for K15t GmbH

Resolved

We monitored our webhook intake and have not observed further interruptions. We are resolving this incident now.
If you have applied changes to content (pages, blog posts, Scroll Documents) during the incident period (01:00 UTC to 21:00 UTC on 22/10/2025) these changes have not triggered updates on your Scroll Sites.
To resolve this you can either modify the affected pages again or trigger a full site update, as described here https://help.k15t.com/scroll-sites/manually-trigger-a-full-site-update
We apologise for the inconvenience.
Posted Oct 23, 2025 - 13:51 CEST

Update

We are continuing to monitor for any further issues.
Posted Oct 23, 2025 - 10:03 CEST

Monitoring

Atlassian has deployed a fix at 20:47 UTC on 22/10/2025. We can confirm the intake of webhooks starting at 21:06 UTC.
Atlassian has also communicated that webhooks for events during the incident will not be delivered. This means that any changes on content (pages, blog posts, Scroll Documents) you have applied during the incident period (01:00 UTC to 21:00 UTC on 22/10/2025) will not trigger updates on your Scroll Sites.
Posted Oct 23, 2025 - 08:33 CEST

Update

The problem report to Atlassian has been acknowledged and being worked on. Atlassian is tracking the incident here https://developer.status.atlassian.com/incidents/41ggtwj1f9f0
Posted Oct 22, 2025 - 14:27 CEST

Identified

We have become aware of a problem with change detection in Scroll Sites.
We have identified that Confluence is not sending any webhooks since 22/10/2025 ~3am GMT. We have informed Atlassian and are awaiting further information.
Posted Oct 22, 2025 - 11:22 CEST
This incident affected: Scroll Apps for Confluence (Scroll Sites).