Templafy Status Page

Apr 1, 2026 · resolved Apr 2

**Investigation** On April 1, 2026, a subset of customers began reporting issues when attempting to open or generate documents through app connectors. As a result, an incident was created at 10:58 AM CET. The engineering team investigated and identified two main issues. Some links from external systems were not directing users to the correct documents, and users encountered errors when accessing certain templates in filtered folders. Further analysis showed that recent changes introduced as part of the new user experience caused inconsistencies in how required data was passed between systems. This resulted in missing information needed to correctly locate and load documents. **Mitigation** Following identification of the issues, the engineering team prioritized restoring functionality. Work began shortly after detection by correcting external link routing and ensuring required data was available before documents were loaded. Temporary mitigation steps were applied to stabilize access while a full fix was prepared. Additional connector flows were also reviewed, including known variations such as the Stuf app connector. **Resolution** The issue was resolved at 5:40 PM CET on April 1, 2026, when fixes were deployed to restore document generation through app connectors. The implemented changes ensured that all required information was consistently available during the document creation process. After deployment, users were able to successfully generate documents and access templates without errors. The solution was validated across affected environments. **Post-Incident Actions** * Feature flag implementations will include options to exclude specific tenants during rollout * Test coverage will be expanded for app connectors, document access, and integration scenarios **Impact and Scope** This incident affected a subset of customers using app connectors within the new end-user experience. Impacted users experienced failures when opening or generating documents, particularly when accessing templates through filtered folders or external links. We sincerely apologize for the disruption caused by this incident. Maintaining a reliable and seamless experience is our highest priority, and we are taking steps to improve our release processes and testing coverage moving forward.

Mar 31, 2026 · resolved Mar 31

**Investigation** On March 31, 2026, at 12:02 PM CET, an issue began affecting access to Templafy for some customers hosted in West Europe \(Production 0\). The issue was detected at 12:09 PM CET through system alerts. The engineering team quickly began investigating and identified that part of the underlying Azure infrastructure supporting the service was not responding as expected. This resulted in temporary access issues for some users. **Mitigation** At 12:41 PM CET, the engineering team took steps to isolate the affected portion of the Azure infrastructure to prevent further impact. Traffic was redirected away from the affected area, allowing the platform to continue operating using healthy resources.  From a user perspective, service was effectively restored at this point, and customers were able to access Templafy as expected. The team continued to closely monitor the system to ensure stability. **Resolution** The affected infrastructure was safely removed from service, and all systems were confirmed to be operating normally. This step reflects full backend recovery and validation, with no additional user impact observed after mitigation. **Post-Incident Actions** We are continuing to review this incident in collaboration with Microsoft Azure to better understand the underlying cause of the infrastructure disruption and to reduce the likelihood of recurrence. **Impact and Scope** This incident affected a subset of customers hosted in West Europe \(Production 0\), who experienced temporary difficulty accessing Templafy between 12:02 PM CET and 12:41 PM CET on March 31, 2026. The root cause was identified as an issue within Azure-managed infrastructure.

Mar 12, 2026 · resolved Mar 12

# Investigation The incident began on March 12, 2026, at 10:17 AM CET, when some users attempting to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices experienced difficulties loading the site. The issue was detected at 1:36 PM CET, after reports indicated that the site could not be accessed successfully from certain mobile clients. The engineering team began investigating immediately after detection. The issue was related to an ongoing infrastructure change where traffic was gradually being moved from the current routing component to a new one. During this transition, a configuration difference in the new system caused some requests to be rejected. This issue mainly affected users accessing the service from mobile devices. # Mitigation Once the cause was identified, the engineering team mitigated the issue by redirecting traffic back to the previous routing component. This rollback restored the previous routing behavior and prevented further request validation conflicts, allowing the team to continue analyzing the routing component configuration. # Resolution The incident was resolved on March 12, 2026, at 2:31 PM CET, once traffic had been fully reverted to the previous infrastructure configuration. Following the rollback, affected users were again able to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices without issues. # Impact and Scope This incident affected users attempting to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices during the migration window on March 12, 2026. The issue occurred during a controlled infrastructure migration and impacted requests routed through the following clusters: * West Europe \(Production 0\) * Australia East \(Production 3\) * West Europe \(Production 5\) Users accessing the service from mobile devices connected to these clusters may have experienced difficulty loading the site during the incident window. # Post-Incident Actions Following the incident, the engineering team reviewed the migration process and identified improvements to the procedures used during infrastructure transitions. These improvements will help ensure smoother migrations and reduce the likelihood of similar issues occurring in the future.

Mar 10, 2026 · resolved Mar 10

## Investigation The incident began on March 10, 2026, at 8:04 AM CET and affected document generation and download functionality for some users. In certain cases, documents could fail to generate when templates contained non-ASCII characters in the file name. Additionally, some downloaded documents appeared corrupted. The issue was detected on March 10, 2026, at 1:58 PM CET, after alerts indicated unusual behavior related to document processing. The engineering team immediately began investigating the issue. During the investigation, the team found that a recent change related to how documents were stored in blob storage within the Dynamics integration had introduced unexpected behavior. This change caused templates with certain characters in their names to fail during document creation and also led to incorrect references to stored documents, which resulted in corrupted downloads. ## Mitigation The engineering team reverted the recent blob storage changes introduced in the Dynamics integration and removed metadata related to template names that contributed to the failures. The team also corrected the document identification and storage logic to ensure documents were saved and retrieved correctly. These steps restored normal behavior for document generation and downloads. ## Resolution The fix was deployed on March 10, 2026, and was successfully rolled out to **West Europe \(Production 0\)** by 3:56 PM CET. Following the deployment, document creation and downloads returned to normal operation. ## Impact and Scope This incident affected document creation and document download functionality for customers hosted on **West Europe \(Production 0\)**. During the incident window from March 10, 2026, at 8:04 AM CET until March 10, 2026, at 3:56 PM CET, users could experience issues generating documents from templates with certain characters in their names or receive corrupted files when downloading documents. ## Post-Incident Actions The engineering team reviewed the incident and identified opportunities to further improve validation around document storage. As part of the follow-up actions: * Automated tests will be expanded to validate storage paths before documents are stored. * Additional validation will ensure that document identifiers and storage locations remain consistent during processing. * The team will continue improving how template name metadata is handled to support a wider range of naming conventions.

Mar 9, 2026 · resolved Mar 9

# Investigation The incident began on March 5, 2026, at 8:04 AM CET and affected the Document Updater functionality for PowerPoint presentations, where users encountered an error when attempting to update presentations. As a result, PowerPoint presentations could not be updated through the Document Updater. The issue was detected on March 9, 2026, at 9:32 AM CET, after reports indicated that users were receiving error notifications when attempting to update PowerPoint documents. The engineering team immediately initiated an investigation to determine the cause of the issue. During the investigation, the team identified that a recently introduced change related to the Templafy Validator functionality for unlocking slides had unintentionally introduced a regression affecting the Document Updater. The change modified the contract used by the VSTO component responsible for processing template configuration. Due to this contract change, VSTO was unable to correctly process the configuration, resulting in errors when users attempted to update PowerPoint presentations. # Mitigation After identifying the cause of the issue on March 9, 2026, at 9:41 AM CET, the engineering team began implementing a fix to restore compatibility with the existing VSTO integration. A corrective code change was prepared. The fix ensured that the contract used by the VSTO component could once again correctly process template configuration required by the Document Updater. # Resolution By 12:05 PM CET on March 9, 2026, the fix had been successfully deployed across all production clusters. Once deployed, the Document Updater functionality for PowerPoint presentations was restored, and users were able to update presentations normally without encountering errors. # Impact and Scope This incident affected the PowerPoint Document Updater functionality, preventing users from updating PowerPoint presentations through the platform. The issue impacted tenants across all production clusters, affecting all tenants using the PowerPoint update functionality during the incident window from March 5, 2026, at 8:04 AM CET until March 9, 2026, at 12:05 PM CET. # Post-Incident Actions The engineering team has reviewed the incident and identified opportunities to improve safeguards around compatibility between platform components. As part of the follow-up actions: • Additional review procedures will be introduced for changes that affect contracts used by client integrations such as VSTO. • The team will investigate approaches for introducing tests that validate backwards compatibility for contract changes, particularly for integrations that rely on existing client-side implementations. • Internal development guidelines will be reinforced to ensure that contract changes are carefully evaluated for potential downstream impact. These improvements aim to reduce the risk of similar regressions in the future.