Singlewire Software experienced a minor incident on April 3, 2024 affecting Android Push Notifications and Rest API and 1 more component, lasting 3h 3m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 03, 2024, 08:43 PM UTC
InformaCast Mobile and Fusion customers may experience issues sending Message Templates and Scenarios when senders do not have view access to all recipients. Investigation We’re investigating a service in our infrastructure responsible for the permissions errors end users are receiving while attempting to send notifications. Mitigation Sending all notifications with administrator-level privileges is not impacted. Next Steps We will provide an update within the hour with additional details on the impact and any recommended actions to take.
- investigating Apr 03, 2024, 09:43 PM UTC
Impact We’ve identified that this issue only impacts users with limited permissions sending scenarios to recipients through scenario messages with site roles. Status Our team has identified the issue and has begun implementing a fix. Mitigation Sending scenarios without site questions should continue to work as normal. If you need to send a notification, prefer one of those channels, or send as an administrator user.
- monitoring Apr 03, 2024, 11:23 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 03, 2024, 11:46 PM UTC
This incident has been resolved.
- postmortem Apr 05, 2024, 06:19 PM UTC
As part of the code changes that went out in our most recent release, we changed the way we assess permissions on a number of our resources, including permissions to recipients on scenario notifications. We erroneously made it so recipients \(users, distribution lists, outbound systems, and device groups\) attached to scenario notifications through site roles that a sender didn’t have access to would trigger a validation error because of the user’s limited permissions. Users should always be able to send scenarios and message templates regardless of their specific access to resources, so we removed the check for these recipient permissions going forward.