Forced change from Classic to Next-Gen cause of chaos

This morning, our 50+ users of our mission-critical app began having many problems, and a total change in User Interface. I logged in to the builder and found our Classic app was now Next-Gen. Our Javascript, CSS, and API connections were missing. The theme assigned to our app was changed. Needless to say, it was very distressing.

About 15 minutes later, the app changed back to Classic, and user experience became normal again.

I have contacted support and not yet received a reply. We’re trying to understand if we need to prepare for a serious business interruption. Or, if this was an unusual experience that won’t likely re-occur.

Have any other Knack customers experienced this?

We experienced the same issue just now. No one notified us about this major upgrade and potential service interruption.

We experienced this interruption also and would like a reply from Knack on this.

From the service page: https://status.knack.com

Another thread states that they don’t plan to eliminate classic apps or force a transition. Seems like insufficient process control on Knack’s Next-gen development may be a real problem for Classic users.

Hi all,

We’re so sorry - a mistake was made with a configuration on a feature flagging system, not an engineering bug or an issue with Next-Gen or Classic development. It will not happen again, and we are not going to force Classic users to switch to Next-Gen only.

Thank you,

Kara

3 Likes