Historique des pannes de Planning Center

1. 5 septembre 2026 à 17:17 UTCinvestigating

   Nous examinons actuellement les alertes selon lesquelles certaines stations inactives pourraient ne pas recevoir de mises à jour en direct après 2 heures d'inactivité (p. ex. changements de modèle). Notre équipe enquête sur la cause de la perturbation et travaille à trouver une solution. L'interaction manuelle avec la station résoudra le problème entre-temps.

2. 5 septembre 2026 à 18:01 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 6 septembre 2026 à 10:28 UTCinvestigating

   Les correctifs mis en œuvre n'ont pas entièrement résolu la question, nous continuons donc d'étudier la cause fondamentale. Les stations Idle peuvent encore manquer les mises à jour en direct (p. ex., changements de gabarit) après 2 heures d'inactivité. Si une station apparaît hors de sa date, cliquez sur le bouton « Démarrer » pour restaurer les mises à jour en direct.

4. 6 septembre 2026 à 17:18 UTCmonitoring

   Un correctif a été mis en place et nous continuons de surveiller les résultats.

5. 6 septembre 2026 à 18:18 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 septembre 2026 à 14:34 UTCidentified

   Les clients peuvent éprouver des problèmes lorsqu'ils tentent de traiter des dons. Notre équipe a identifié la cause et travaillé sur une résolution.

2. 2 septembre 2026 à 14:37 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 2 septembre 2026 à 14:39 UTCmonitoring

   Nous avons déployé une correction et voyons les taux d'erreur diminuer. Les dons devraient être traités avec succès maintenant, et nous continuerons à surveiller.

4. 2 septembre 2026 à 15:12 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 12 juillet 2026 à 16:16 UTCinvestigating

   Nous examinons les rapports de certaines stations ne pouvant pas charger des Check-Ins et montrant une erreur 403. Notre équipe enquête sur la cause de la perturbation et travaille pour résoudre le problème.

2. 12 juillet 2026 à 16:25 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

3. 12 juillet 2026 à 16:39 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 12 juillet 2026 à 19:27 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 11 juillet 2026 à 18:52 UTCinvestigating

   Les utilisateurs peuvent éprouver des problèmes de connexion à leurs comptes. Notre équipe enquête sur la cause de la perturbation et travaille à rétablir le plein accès.

2. 11 juillet 2026 à 19:09 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 11 juillet 2026 à 19:09 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 12 juillet 2026 à 01:25 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juin 2026 à 21:24 UTCresolved

   Les services ont connu une brève panne de 3 minutes en raison des délais de requête de la base de données pendant la maintenance prévue. La question a été résolue à 13 h 50, heure du Pacifique, et les services sont stables depuis. Nous nous excusons pour toute perturbation que cela aurait pu causer.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 juin 2026 à 14:17 UTCinvestigating

   On sermon channels livestreaming with a persistent YouTube embed link, congregants may see intermittent video disruptions when viewing on Church Center (both app and web). We are currently investigating.

2. 7 juin 2026 à 15:15 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 7 juin 2026 à 15:32 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 à 00:25 UTCinvestigating

   We are currently investigating an issue where new users are unable to add their first name during the initial login process on Church Center app. This may affect the ability to complete the setup of a new account on the latest version of the app (2026.5.6).

2. 13 mai 2026 à 01:56 UTCidentified

   We've identified the root cause of the new account creation issue in the Church Center app and have a fix in progress. In the meantime, new customers can create their Church Center account without issue on Church Center web.

3. 13 mai 2026 à 11:00 UTCresolved

   We have resolved the issue affecting new account creation in the Church Center app. To receive the update, force close the app and reopen it — this may take a few attempts. You can confirm you have the latest version by checking your profile for v2026.5.6 Build#5792 Update f212.

1. 10 mai 2026 à 19:49 UTCinvestigating

   Our team is aware of and looking into some reports of event registrations unable to be completed.

2. 10 mai 2026 à 19:51 UTCidentified

   Our team has identified the issue preventing some event registrations from being completed and are working on a fix.

3. 10 mai 2026 à 20:13 UTCresolved

   This incident has been resolved and registering for events should be back to fully operational.

1. 15 avril 2026 à 13:40 UTCidentified

   We've identified the cause of crashes affecting Services mobile app users on iOS 17 and below and are preparing a fix for App Store submission.

2. 15 avril 2026 à 15:09 UTCidentified

   Our team is actively working on a fix for this issue affecting Services mobile app users on iOS 17 and below, and hope to have a patch submitted to the App Store with an expedited review soon.

3. 15 avril 2026 à 16:23 UTCidentified

   We have a fix in place, and have submitted to the App Store for expedited review. Once approved, this will available in a new App version update, 6.8.2

4. 15 avril 2026 à 19:49 UTCidentified

   Update: Our fix is currently in App Store review with Apple. Once approved, this will available in a new App version update, 6.8.2

5. 15 avril 2026 à 22:52 UTCidentified

   We are continuing to monitor the status of the App Store review with Apple. Once approved, this will available in a new App version update, 6.8.2

6. 16 avril 2026 à 01:14 UTCresolved

   The fix has been approved and shipped to the App Store in the form of a new version update, 6.8.2 This issuwchasxnow been resolved.

1. 9 avril 2026 à 15:44 UTCinvestigating

   Users may experience an error message when attempting to send chat messages in the Church Center app. Our team is currently investigating the issue to identify the cause and restore full functionality.

2. 9 avril 2026 à 16:10 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 9 avril 2026 à 16:22 UTCresolved

   Our team has completed a fix, and sending messages through Chat will no longer trigger an error.

1. 18 mars 2026 à 13:37 UTCinvestigating

   Customers may experience issues with certain buttons not being visible unless hovered over, such as "New Batch" or "Enter Pledge." Our team is working to resolve the issue promptly.

2. 18 mars 2026 à 13:58 UTCresolved

   This has been resolved. All buttons are visible again.

1. 3 mars 2026 à 15:18 UTCinvestigating

   Customers may experience difficulties accessing the People product. Our team is currently investigating the cause of this disruption.

2. 3 mars 2026 à 15:28 UTCmonitoring

   People is back up and running. We’re currently evaluating whether any follow-up actions are needed.

3. 3 mars 2026 à 15:56 UTCresolved

   This has been fully resolved.

1. 26 février 2026 à 19:02 UTCinvestigating

   Users may experience issues with Calendar Kiosks not displaying events. Our team is currently investigating the cause of this disruption.

2. 26 février 2026 à 19:13 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 26 février 2026 à 19:55 UTCresolved

   This incident has been resolved.

1. 14 février 2026 à 22:08 UTCinvestigating

   Users may experience difficulties printing from the Services mobile app as the AirPrint option is not showing the native print options as expected. We are currently investigating the issue.

2. 14 février 2026 à 22:50 UTCidentified

   We have identified the issue and are working on a fix via a new app version update.

3. 15 février 2026 à 02:51 UTCidentified

   Our team has implemented a fix for plan printing in the Services mobile app that is currently under App Store review. Once approved it’ll be available in the app store for download.

4. 15 février 2026 à 05:12 UTCidentified

   Our team has submitted for an expedited review from the App Store for a fix that addresses an AirPrinting issue within Services mobile. Once approved a new Services mobile version (iOS) will release to the App Store immediately and be available for download.

5. 15 février 2026 à 14:01 UTCidentified

   Our patch fix is still awaiting review from the App Store. Once the build has been approved by Apple, you will be able to download the new version (6.7.7) in the App Store with a fix for airprinting. In the meantime, if you are needing to print your order of service, you can print from the mobile browser or services web view. We'll keep you updated on the status.

6. 15 février 2026 à 16:34 UTCresolved

   This incident has been resolved. You can get the updated Services mobile iOS app version (6.7.7) in the App Store, which includes a fix for AirPrinting.

1. 22 janvier 2026 à 20:38 UTCidentified

   We are currently experiencing email delivery issues to Outlook/Microsoft 365 addresses due to a temporary error on Microsoft's side. We are actively monitoring the situation and emails are being retried automatically and should be successfully sent once Microsoft fixes the issue. We'll post an update once services are restored to normal.

2. 23 janvier 2026 à 13:54 UTCresolved

   Microsoft has resolved their issue, and our delivery rates have returned to normal. Outgoing emails that had previously bounced during this incident have been successfully delivered.

1. 17 janvier 2026 à 17:03 UTCinvestigating

   We are currently investigating issues with Music Stand sessions not syncing on iOS devices when using the Pusher connection path. - Multipeer connections remain unaffected.

2. 17 janvier 2026 à 17:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 janvier 2026 à 17:45 UTCidentified

   We’ve identified the cause of page turns not syncing for Music Stand Sessions joined via Pusher, and we’re working on a fix that will ship in an upcoming App Store update. If you’re currently in an active service on iOS, switch your Session connection to Multipeer to keep Sessions running without interruption.

4. 17 janvier 2026 à 19:12 UTCidentified

   Our team is actively working on getting a new iOS version build with a fix to address Music Stand sessions not syncing for specific connection types. If you’re currently in an active service on iOS and need sessions, switch your Session connection to Multipeer to keep Sessions running without interruption. We'll update the status every 30 minutes to keep you up-to-date.

5. 17 janvier 2026 à 19:49 UTCmonitoring

   A fix has been verified via our internal builds and an approved fix has been sent to the App Store for expedited review. Once the build has been approved by Apple, you will be able to download the new version (4.7.3) in the App Store with a fix for synced session connections. We'll keep you updated every 30 minutes on the status.

6. 17 janvier 2026 à 20:34 UTCmonitoring

   Our implemented fix is still awaiting App Store review before being made available in the App Store for download. We'll continue to update this status on the status of the Store review.

7. 17 janvier 2026 à 21:25 UTCmonitoring

   Our patch fix is still awaiting review from the App Store. Once the build has been approved by Apple, you will be able to download the new version (4.7.3) in the App Store with a fix for synced session connections. In the meantime, if you are needing to use sessions for a Saturday night service, switch your Session connection to Multipeer to keep Sessions running without interruption. We'll keep you updated on the status.

8. 17 janvier 2026 à 23:18 UTCmonitoring

   Our patch fix is still awaiting review from the App Store. In the meantime, if you are needing to use sessions for a Saturday night service, switch your Session connection to Multipeer to keep Sessions running without interruption. We'll continue updating the status page on the App Store review status.

9. 18 janvier 2026 à 00:45 UTCmonitoring

   Update: Our Music Stand connected sessions fix is still waiting App Store review with Apple. Once reviewed and approved we'll update this status page. If you are needing to use sessions for a Saturday night service, switch your Session connection to Multipeer to keep Sessions running without interruption.

10. 18 janvier 2026 à 02:26 UTCmonitoring

    Update: We’re awaiting App Store approval for a release that fixes Music Stand Sessions sync. We’ll keep this incident updated.

11. 18 janvier 2026 à 04:17 UTCmonitoring

    We’re still awaiting App Store approval for a release that addresses an issue with Music Stand Sessions sync using Pusher connection. In the meantime, you can use sessions with "multipeer" connection to utilize the feature without interruption.

12. 18 janvier 2026 à 07:17 UTCmonitoring

    Update; App Store approval is still pending review. We’ll continue to monitor the status of the review which addresses an issue with Music Stand sessions around syncing page turning. In the meantime, you can use sessions with "multipeer" connection to utilize the feature without interruption.

13. 18 janvier 2026 à 11:24 UTCmonitoring

    Our patch fix is still awaiting review from the App Store. Once the build has been approved by Apple, you will be able to download the new version (4.7.3) in the App Store with a fix for synced session connections. In the meantime, if you are needing to use sessions for service, switch your Session connection to Multipeer to keep Sessions running without interruption. We'll keep you updated on the status.

14. 18 janvier 2026 à 17:17 UTCresolved

    This incident has been resolved and the App Store has approved our patch fix that addressed a bug with Music Stand sessions not correctly syncing page turns across devices. Update to our latest build in the App Store Music Stand(4.7.3) to receive the fix.

1. 13 novembre 2025 à 18:38 UTCinvestigating

   Our team is investigating users experiencing issues accessing Rehearsal Mix search features and files not playing correctly or display licensing errors.

2. 13 novembre 2025 à 19:00 UTCresolved

   The Multitracks Team has implemented a fix that fixed an issue with Multitracks searches being down as well as RehearsalMix files returning an error message. Things should be back to normal.

1. 9 novembre 2025 à 15:04 UTCinvestigating

   Users may experience errors or degraded performance when accessing services reliant on the Multitracks API. We are currently investigating the issue to restore full functionality.

2. 9 novembre 2025 à 15:25 UTCidentified

   The issue has been identified and our team is working on a fix.

3. 9 novembre 2025 à 15:42 UTCresolved

   We experienced a service disruption caused by an unexpected spike from outbound API requests from our system to Multitracks. This led to instability in both their API and our own services that rely on it. A fix has been implemented on our side, and all services should be back to normal.

4. 13 novembre 2025 à 21:31 UTCpostmortem

   # **Post-Mortem: Service Disruption Caused by Excessive Outbound API Requests to Multitracks** **Date of Incident:** November 9, 2025 **Duration:** ~1 hour **Impacted:** MultiTracks integration; indirect impact to Services and Check-Ins ## **Overview** On November 9, Planning Center experienced a disruption in our MultiTracks integration caused by an internal change to our caching logic. This change unintentionally triggered a large spike in outbound API requests to MultiTracks, which led to their service throttling our traffic. The resulting failures also caused secondary errors in Planning Center services that rely on responses from that API. This issue was rooted in Planning Center’s system behavior, and we take full responsibility for the impact. ## **What Happened** A caching pattern change dramatically increased the number of API requests we sent to MultiTracks. Their service began throttling our traffic, and our retry behavior amplified the load on both systems. This led to elevated errors in the MultiTracks integration and related Planning Center processes. The impact to customers was somewhat minimized because Music Stand apps use local caching, but some experienced errors, slow responses, or missing data. ## **Resolution** We quickly identified the regression and deployed a revert of the caching change. Once reverted, our outbound traffic returned to normal and MultiTracks’ throttling stopped, allowing dependent systems to recover. ## **Root Cause** * A caching change that generated excessive outbound API requests * Retry and timeout behaviors that worsened cascading failures ## **Preventive Actions** 1. Review and tune third-party timeouts to avoid cascading failures 2. Improve graceful degradation strategies for external dependencies 3. Enhance pre-deployment checks for changes affecting outbound request volume ## **Current Status** The MultiTracks integration is stable. We are implementing the above improvements to prevent similar issues and ensure our systems remain resilient even when dependencies become unstable.

1. 28 octobre 2025 à 15:29 UTCinvestigating

   We're investigating delays in processing background tasks across Planning Center.

2. 28 octobre 2025 à 15:43 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 28 octobre 2025 à 15:52 UTCresolved

   This incident has been resolved.

1. 23 octobre 2025 à 16:21 UTCinvestigating

   We are currently investigating this issue.

2. 23 octobre 2025 à 17:27 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 23 octobre 2025 à 23:11 UTCidentified

   We have a fix for this issue and have submitted a new version of the Church Center app that includes that fix. That version is currently being reviewed by the iOS app store and will be released as soon as it is approved.

4. 24 octobre 2025 à 12:06 UTCresolved

   This incident has been resolved.