Is there an Templafy outage?
Templafy status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Templafy.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Templafy Email Signature Server | Active |
| Email Signature Server | Active |
| Templafy Hive | Active |
| Account Management | Active |
| Add-in Management | Active |
| AI Assistant | Active |
| Authentication | Active |
| Email Signature | Active |
| Engage | Active |
| Integrations | Active |
| Library & Dynamics | Active |
| Productivity | Active |
| Resource Management | Active |
| User Management | Active |
| Templafy One | Active |
| Public API | Active |
| WebApp | Active |
View the latest incidents for Templafy and check for official updates:
Description: The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.
Status: Resolved
Impact: Minor | Started At: Nov. 1, 2024, 12:38 p.m.
Description: **Incident Initiation** To improve the automation and security of package management, the engineering team implemented a series of changes. These updates included expanding the status options for each package and involved a database migration. However, the changes unintentionally caused the endpoint responsible for retrieving current packages for users to incorrectly exclude third-party packages. Consequently, these packages were removed from users' computers during the next Templafy Desktop run, making the associated Add-ins unavailable in Office applications. This change was deployed across all environments at 8:20 AM CET on October 23, 2024, though it only started impacting users after the Templafy Desktop component triggered a package update. The issue was first reported at 11:44 AM CET. **Investigation** The incident was placed at 12:10 PM CET, when the software engineering team was notified. The root cause was quickly identified and the engineering team immediately started implementing a fix to ensure the endpoint responsible for retrieving Add-ins correctly included third-party packages. **Impact and Scope** The incident impacted all regions but affected only specific tenants with third-party Add-ins installed. Among these, only users whose Templafy Desktop triggered a package update within the incident timeframe were affected. **Resolution** By 3:14 PM CET, the code fix was successfully deployed across all production environments. This update allowed the Templafy Desktop component to retrieve and reinstall third-party Add-ins, enabling users to access them again following a Templafy Desktop synchronization. **Post-Incident Actions** The engineering team has commenced an extensive review to expand test cases for package delivery, activation, and security assertion, ensuring future enhancements to package functionality do not impact the integrity and stability of existing configurations.
Status: Postmortem
Impact: Major | Started At: Oct. 23, 2024, 10:21 a.m.
Description: Incident Initiation: The issue started on September 20, 2024, at 10:54 AM CET but was detected on September 23, 2024, at 6:02 PM CET. On September 24, 2024, at 2:37 PM CET, the incident response process was initiated after users reported that manually configured User claims in the SAML2 authentication protocol within the Hive environment were no longer being recognized. The issue caused users to lose their User Claims when logging in via SAML2 authentication, due to a mismatch between customer configurations and the system's case-sensitive claims checks. Investigation: The issue affected only a subset of customers, making it difficult to reproduce and investigate at first. Engineers closely examined the system and identified that the problem was caused by an external package update that implicitly upgraded the "Microsoft.IdentityModel.\*" packages from version 7.x to 8.x. This update introduced case sensitivity in claims checking, which conflicted with how some customers had configured their SAML2 claims. Once the root cause was pinpointed, the team began working on a solution to mitigate the issue. Resolution: After identifying the root cause, the configuration was adjusted to account for the case-sensitive claims checks. Normal functionality was restored, and users could resume all affected operations, resolving the incident on September 24, 2024, at 10:31 PM CET. Post-Incident Actions: Moving forward, we will focus on improving our monitoring and testing processes for package updates. Closer collaboration with customers and better detection mechanisms will help us identify and resolve similar issues more efficiently.
Status: Postmortem
Impact: Major | Started At: Sept. 24, 2024, 12:54 p.m.
Description: Incident Initiation: On September 4, 2024, at 11:59 AM CET, an anomaly was detected in the internal component of Hive, which initiated an incident. The issue specifically affected the campaign designer, causing newly uploaded images to disappear for users. Investigation: The engineering team immediately began investigating the issue. It was discovered that the newly uploaded images were not being transferred to long-term storage due to a malfunction in the storage service. The root cause was identified as a misconfiguration introduced during a recent update to the image handling system. Mitigation and Resolution: A temporary mitigation was put in place to ensure that images uploaded after the detection of the issue were properly stored. Following this, a correction was developed and deployed at 01:44 PM CET to restore the application's functionality. This fix addressed the underlying configuration error, and the system returned to normal operation. Impact and Scope: The incident impact was on across all regions and affected only certain tenants with a specific configuration attempting to upload images during the incident window. Post-Incident Actions: Procedural improvements will be implemented, including enhanced monitoring of storage services. The engineering team is also reviewing the update process to prevent similar misconfigurations.
Status: Postmortem
Impact: Major | Started At: Sept. 4, 2024, 10:12 a.m.
Description: On August 23, 2024, at 09:37 AM CET an incident was started due to previews not generating in the Templafy One environment. Engineers started investigating the issue and discovered that the number of messages exceeded the capacity of the preview processing system that was initially configured. After adjusting the configuration, the messages began processing correctly again. This action restored normal function to the application allowing users to generate previews, resolving the incident at 10:07 AM CET.
Status: Postmortem
Impact: Major | Started At: Aug. 23, 2024, 7:59 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
