Is there an GoFormz outage?
GoFormz status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for GoFormz and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for GoFormz and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for GoFormz.
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 |
|---|---|
| API (v2) | Active |
| Automated Workflows | Active |
| Email Delivery | Active |
| Mobile Sync API | Active |
| Web App | Active |
| Web App - Support Chat Bubble | Active |
| Mobile Apps | Active |
| Andoird App | Active |
| iOS App | Active |
| Windows App | Active |
View the latest incidents for GoFormz and check for official updates:
Description: **Timeline**: Sunday 12/19/21 6:28 am - 8:32am PST **Root Cause Analysis**: After a detailed investigation, the GoFormz Engineering team determined that one of the database pools had insufficient storage space, due to unreleased data during our normal database maintenance. This resulted in a lack of space available for a subset of customers. **Mitigation**: Immediate action was taken to increase the available space on the database pool. Additionally, alerts were updated to include total available storage space.
Status: Postmortem
Impact: Major | Started At: Dec. 19, 2021, 4:25 p.m.
Description: **Summary**: On 11/16, code containing a defect was released. This code was not in use until 12/02, when customers attempting to generate a pdf saw service errors or latency. **Root Cause Analysis**: After a detailed investigation, the GoFormz Engineering team determined that there was an underlying code defect in a 3rd-party pdf tool that caused a higher-than-normal amount of CPU. During high traffic, this defect created a deadlock and resulted in several servers stalling when attempting to generate a pdf. Consequently, our API and Web services experienced errors and timeouts, and our backend queues experienced an increase in service latency. **Mitigation**: Immediate action was taken to scale out the pdf services, allowing for the increase in CPU to be handled. Complete mitigation was accomplished when the engineering team was able to correct the code defect and deploy a hotfix to all pdf services. **Next steps**: While this issue is resolved, GoFormz Engineering is continuing to closely monitor each service for errors or instability.
Status: Postmortem
Impact: Minor | Started At: Dec. 3, 2021, 4:37 p.m.
Description: **Summary**: On 11/16, code containing a defect was released. This code was not in use until 12/02, when customers attempting to generate a pdf saw service errors or latency. **Root Cause Analysis**: After a detailed investigation, the GoFormz Engineering team determined that there was an underlying code defect in a 3rd-party pdf tool that caused a higher-than-normal amount of CPU. During high traffic, this defect created a deadlock and resulted in several servers stalling when attempting to generate a pdf. Consequently, our API and Web services experienced errors and timeouts, and our backend queues experienced an increase in service latency. **Mitigation**: Immediate action was taken to scale out the pdf services, allowing for the increase in CPU to be handled. Complete mitigation was accomplished when the engineering team was able to correct the code defect and deploy a hotfix to all pdf services. **Next steps**: While this issue is resolved, GoFormz Engineering is continuing to closely monitor each service for errors or instability.
Status: Postmortem
Impact: Minor | Started At: Dec. 3, 2021, 4:37 p.m.
Description: During Tuesday’s (9/21 at 1:15pm PDT) production release, a configuration issue was introduced across various services that resulted in a degraded performance of some customer Workflows under heavy load. GoFormz Engineering identified the root cause of this issue and released a fix Wednesday morning (9/22 at 9:30am PDT). Recommended Action: Workflows that failed during this time may need to be manually rerun in the GoFormz Web App. Additionally, Connected Apps may need the re-authenticated from the Connected Apps page of an ‘Unauthorized Error’ shown or if the status for a particular connection is red.
Status: Resolved
Impact: Minor | Started At: Sept. 22, 2021, 2 p.m.
Description: GoFormz engineering has identified an error with a recent production release. The faulty code has been rolled back, and services are beginning to return to normal operations.
Status: Resolved
Impact: Minor | Started At: July 28, 2021, 4:30 p.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.
