Customers using Zscaler might experience issues with multiple functionalities due to blocked QUERY request

Update timeline

1. identified Oct 28, 2026, 02:37 PM UTC

   We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.

2. monitoring Oct 28, 2026, 07:20 PM UTC

   The incident has been successfully mitigated, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.

3. resolved Oct 28, 2026, 08:28 PM UTC

   The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.

4. postmortem Oct 30, 2026, 12:30 PM UTC

   ## Investigation On October 28, 2026, at 3:11 PM CET an issue was detected, following reports from affected customers. The engineering team investigated the reported behavior and identified that a recent migration to the HTTP QUERY method had introduced compatibility issues with certain Zscaler configurations that did not permit this request method. ## Mitigation Following the identification of the issue, the engineering team initiated mitigation efforts to restore the affected functionality. The team determined that reverting the affected endpoints to the previously supported HTTP POST method would restore compatibility with the impacted network configurations. The engineering team implemented the necessary changes to address the issue and restore normal functionality for affected customers. ## Resolution On October 28, 2026, the engineering team completed the rollback from HTTP QUERY to HTTP POST for the affected endpoints. This restored compatibility with the impacted Zscaler configurations and resolved the functionality issues experienced by affected customers. The incident was resolved at 9:26 PM CET on October 28, 2026. ## Post-Incident Actions To reduce the likelihood of similar incidents, we are reviewing our approach to introducing new HTTP request methods, with particular attention to compatibility with enterprise network security solutions. These measures are intended to improve early detection and strengthen platform reliability across different customer environments. ## Impact and Scope The incident affected a subset of enterprise customers using Zscaler with network configurations that restricted the HTTP QUERY method. Affected customers experienced disruptions to multiple Templafy functionalities, including difficulties performing daily tasks that relied on the impacted requests. The impact was limited to customers using the affected network configurations rather than all Templafy users. We sincerely apologize for the disruption caused by this incident. Maintaining a reliable and seamless experience for our customers remains a top priority. We are committed to continuously improving our platform's compatibility, monitoring, and stability to help prevent similar issues in the future.