Is there an Templafy outage?
Templafy status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 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: On August 14, 2024, at 1:56 PM CET, an incident was initiated when the email signature synchronization process took longer than usual to complete, causing delays in distributing email signature updates to end users. At 4:02 PM CET, the team reverted to a previous version of email signature synchronization process, confirmed that the synchronization was running within the desired parameters, and deployed it to all production environments. The team continued to monitor system performance and, after ensuring everything was operating at the desired performance metrics, marked the incident as resolved at 4:42 PM CET. The engineering team will investigate to identify the root cause of the issues in the email signature synchronization process. Additionally, they are focusing on further quality automation and performance checks to prevent similar incidents in the future.
Status: Postmortem
Impact: Minor | Started At: Aug. 14, 2024, 12:05 p.m.
Description: On July 25, 2024, at 10:31 AM CET, an incident was initiated due to a problem where admins were having problems using the space administration functionality. This issue was specifically related to the assignment of space owner access flow, which could potentially remove all space owners if a user attempted to remove a subset of the owners. The engineering team initiated an investigation upon the incident creation and identified that the issue was caused by a newly created UI component. After isolating the problem the team then moved into the mitigation phase and worked diligently to integrate a solution across all impacted subsystems. At 12:56 CET they managed to deploy the fix to all the production environments. The issue was confirmed to be fixed and management operations for spaces was restored. We apologize for the disruption and remain committed to ensuring the reliability and stability of our services.
Status: Postmortem
Impact: Minor | Started At: July 25, 2024, 8:31 a.m.
Description: On July 22, 2024, at 11:04 AM CET, an incident was initiated when the email signature synchronization process took longer than usual to complete, causing delays in distributing email signature updates to end users. The engineering team quickly initiated an investigation and identified that the issue was caused by message processing. The problem arose due to a recent migration to a new messaging framework, which began to exhibit performance issues. To mitigate the problem, the team reverted to the previous messaging framework, confirmed that the synchronization was running within the desired parameters, and by 1:07 PM CET, managed to deploy the fixed version to all production environments. The team continued to monitor system performance and, after ensuring everything was operating at the desired performance metrics, marked the incident as resolved at 6:27 PM CET. The engineering team is currently conducting extensive tests to identify the root cause of the performance issues in the new messaging framework. Additionally, they are focusing on further quality automation and performance checks to prevent similar incidents in the future.
Status: Postmortem
Impact: Minor | Started At: July 23, 2024, 9:13 a.m.
Description: On June 20, 2024, at 7:58 PM CET, an incident was initiated because uploading of presentation templates were not fully processed due to the failure of slide preview generation. The issue was introduced at 2:05 PM CET and detected by a user at 4:50 PM CET while using document creation public API. The engineering team began the investigating at 8:05 PM CET. The incident was confirmed to be affecting more than one tenant and a large number of users, causing a high rate of exceptions/errors in system logs. At 8:15 PM CET, the engineering team identified that the recent release changes, specifically a minor version increase in an external library, as the potential cause and began reverting these changes. By 9:00 PM CET, the mitigation changes has been validated in our testing environment and prepared for production release. At 9:49 PM CET, the issue was resolved on West Europe \(Production 0\). This incident serves as a reminder of the importance of thorough testing and monitoring, especially after release changes. The engineering team's prompt response and effective mitigation strategies helped to minimize the impact and ensure a swift resolution.
Status: Postmortem
Impact: Major | Started At: June 20, 2024, 6:10 p.m.
Description: On May 28, 2024, at 10:45 AM CET, an incident impacting all users utilizing the Dynamics & Library system within the West Europe \(Production 1\) environment was detected. The issue caused the system to have degraded performance, causing the users to experience slow responses or even timeouts. The engineering team quickly discovered that the degraded performance was caused by the SQL server being under a heavy load due to a reindexing operation. The reindexing operation was part of a migration process that the engineering team was rolling out. At 11:00 CET, as an immediate mitigation, the engineering team initiated the capacity increase of the SQL server. By 11:05 CET, the extra resources to the SQL server were successfully allocated. At this time, the application performance restored to normal parameters, and the application users were no longer impacted. By 12:37 CET, the incident was resolved after the engineering team successfully applied the migration and confirmed it was working as expected. We are reviewing and enhancing our internal procedures for migrations to ensure that similar issues are prevented in the future.
Status: Postmortem
Impact: Major | Started At: May 28, 2024, 8:45 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.
