Knack Outage History

Our engineering team has located the root cause and applied a fix to Flows. Actions not triggered earlier will be processed.

On August 6th at 6pm ET, we resolved this issue. We sincerely apologize for the disruption this caused to your work and workflows. The root cause was a change deployed on Thursday, July 30th around 10am ET that caused some equation fields, text formula fields, and aggregation fields (such as counts, sums, mins, and maxes) in some apps to not consistently recalculate when their source records and fields were updated. All formula, equation, and aggregation fields will are now properly recalculate when source records and fields are updated. If you believe your app may have stale field values from the affected window, we recommend triggering a bulk update on the relevant source table to prompt recalculation -- our support team can walk you through this if needed. We appreciate your patience throughout this process. For more details or assistance, please contact our Support team.

Some customers were unable to create or edit records on August 1st. Customers saw the following error: 400: 167a79500000000000000002 is invalid for field_XXXX (Updated By) connecting to object_X This issue has been resolved, and users should be able to create records now

The fix for this issue has been deployed to all affected customers/apps. Records will update correctly on incremental changes, formula fields will recalculate as expected on the next update that triggers the formula, and behind-the-scenes jobs will run cleanly moving forward. If there was an automated-process that 1) ran since Saturday, August 1st at 10am ET and 2) is on a Weekly, Monthly, Yearly, or a custom schedule and 3) was not for sending emails (email-sending was unaffected by this issue), we recommend reviewing and re-running that automated-process. We take any customer-impacting issue seriously and apologize for the disruption this may have caused your business. Please continue to reach out to our team if there are outstanding questions by emailing [email protected]

We have received reports that the issue causing some users to see a blank page when accessing their Live Apps has been resolved. We are no longer seeing widespread impact, and this incident is now considered resolved. If you continue to experience issues, we recommend trying an alternate network or contacting your ISP for further assistance. Thank you for your patience while this was ongoing.

The issue affecting access to the Builder has been fully resolved. All systems are operating normally. Thanks for your patience while we worked to address this.

This issue has been resolved. Access to both Classic and Next Gen has been fully restored for all affected accounts. The issue was caused by a problem with one of our third-party providers and has since been addressed. How We're Preventing This Moving Forward: The logic that determines "Classic" vs. "Next Gen" access will be completely removed from being owned by a third-party vendor, and will be owned by Knack's internal team. This eliminates all exposure our customers have from this third-party vendor publishing a bug/problem that caused this issue. Thank you for your patience while we worked to resolve this.

Our engineering team has fixed the issue and services are back to normal. If you notice any more issues after this point please reach out to our support team through the available channels.

Our Engineering team has been actively monitoring and testing all Knack services, and we’re happy to report that functionality has returned to normal. The underlying AWS incident remains open as their teams continue to run additional tests and validations, but Knack appears to be fully recovered from the impact. Thank you for your patience while this was resolved.

Today, from 11:08am ET to 11:26am ET, a misconfiguration in our feature-flagging tool caused all customer apps to default to the Next-Gen experience only. During this time, attempts to access Classic URLs resulted in errors. At 11:27am ET, the issue was fully resolved, and all access has returned to normal: - Customers with Classic-only access now have Classic-only access restored. - Customers with Next-Gen-only access now have Next-Gen-only access restored. - Customers with both Next-Gen and Classic access now have both restored. We apologize for the disruption and appreciate your patience.