I’ve been a knack dev for over 7 years. Whilst you can and we have built some excellent solutions, often with css and jQuery as well as Zapier api supporting custom functions.
The pain of issues from upgrades I’m feeling now that’s not in my control or of my making is now a deal breaker!
5 days of no support and customers expecting results, using a platform app that’s had no changes for 2 years is now broken! And this is the core platform calculations,noy any JS or Api calls, just a basic sum formula! I might have to resort to JS to fix the issues.
They’ve at least acknowledged the bug and exculated. Try telling that to a customer.
I don’t believe they’ve fulfilled any robust UAT, and that’s not acceptable to me.
I’m glad people are contributing to this thread to show knack the impact this is having. I think they make the assumption everyone using the platform is developing for themselves or their own organisations. As people have said in the thread we are developing for paying customers and large organisational customers who use and need the apps every day for critical business.
When it breaks they blame us.
It impacts our businesses.
It kills our reputation.
It burns our work time.
It’s simply not acceptable for us to turn around to our customers and say knack has broken your application and given us no timeframe for when it will be fixed.
Feeling the pain of everyone and good luck sorting this avoidable mess out.
@Marek Re your statement: " If there are any particular issues that you’re coming across, please do submit a ticket at firstname.lastname@example.org that we could investigate and get back to you when we have any insights"
I submitted a ticket two weeks ago and have had nothing back other than an automated acknowledgement. If you are going to depend on support tickets for feedback, you need to ensure you have the capacity to handle them. I note that Knack is recruiting, but as far as I could see not for support staff - maybe something think about?
The value of this community is to tell me that I am NOT ALONE!
In fact this upgrade does not fulfill its mission. In some cases, performance is worse (and not consistent).
The support were helpful after the upgrade but suddenly disappeared for the last 7 days.
Hey there everyone just want to jump back in. We’re aware that performance in the new environment is an issue, and we’re also aware that support ticket times are long. These issues are, as you can imagine, related.
Starting with performance, this is a thing we’ve discussed throughout every layer of the company and with all levels from leadership down. It’s our biggest priority, getting this not just back to what you expect, but better, because that’s what we were aiming for with the upgrade.
With support response times, we’re also aware. We’re working on this in a few different ways. Firstly, from an engineering standpoint getting the performance issues knocked out will reduce inbound ticket volume, which increases our response time. We’re also hiring more in support pretty aggressively (If you have someone you’d like to recommend it to, keep an eye out for our jobs page!) to smooth out bumps like this from a response time angle. We don’t like it taking that long to get back to issues either, and we’re sorry that you’re getting that experience right now.
We experienced 3 different issues with the upgrade that we are aware of. The first issue took over 1 month to resolve, the second issue was intermittent and not officially resolved but went away (how does that happen?) and the third was not resolved but we put our own work around in place to keep operating. To compound this the lack of responsiveness from Knack was almost scary considering we run a chunk of our day to day operations on the platform. My big question is, should we consider another platform? We are a Pro customer, 4+ years in with 50,000 records in the app. I don’t necessarily want to start over but I’d rather do it on my schedule in the event something goes south.
I might be biased, but I would prefer you not consider another platform. Like I said above, we’re really aware that our communication was weak throughout this rough period. That was compounded by these issues creating more support volume than was possible for our pool of employees. We’re already working at hiring both people who can manage communication a bit better and more support employees, as well as those of us that are here being more active in more communication channels.
An issue taking over a month to resolve is something that is definitely frustrating, but I’m certain as you know that there were some pretty huge showstoppers that might’ve gotten in the way of the fix, or the fix may have just been difficult. Sometimes software issues can be more difficult to trace or resolve, sometimes they can be “easy fixes” but the ones we think are easiest often aren’t because of back end interdependencies. It doesn’t make it easier for you, which I get and I’m sorry for.
We’ve got lots of plans for the future that also involve even more internal testing for things than we already do, to help ensure that once we’ve got everything performing swimmingly it stays a smooth ride.
So ultimately: It’ll be up to you whether you want to look elsewhere, but we’d love it if you stuck around to see how great it can get.
We get this Bill, and we want you to win. But I have 25 live apps used every day by paying customers with 500k records in use. The idea that the only issues I ever have with the apps are when you guys break the BAU is bizarre. It’s not a beta platform, it’s an enterprise-level product which is business-critical for many of your customers. Of course you want to grow, reduce your tech debt and improve your capability, but you simply cannot be cavalier with day-to-day stability. I and I know many other knack customers think you have been even if this was not your intent or desire. It rocks confidence and I see why Scott is considering walking. I am currently building a POC for a new product and I too am now seriously looking at other platforms.
Today (3) records on our employee table had incorrect values for their vacation records. For some reason they are calculated in the 1000s rather than a couple days. Nothing has changed on our end and for the rest of the employees their records look fine. This is a simple group sum, nothing elaborate going on. I have reported this as a defect and hope to hear something soon. We are slowly losing faith in Knack to manage our data. The other side of this is the responsiveness from Knack. If this is resolved quickly, that would be fine, but so far I’ve submitted 3 defects, one had our texting component of the app down for over a month until it was fixed. The second is still unresolved after over a month and the most recent, well time will tell…
Where can we find documentation regarding known issues with the new ‘upgraded’ environment. I, like so many other users apparently, work with multiple clients and apps and have been a fan of the platform for years, but unfortunately the lack of tools to troubleshoot and resolve intermittent performance issues and the lack of transparency regarding what is causing the issues is forcing me to no longer recommend Knack. Selling an organization on using a platform or software is difficult enough but when even the simplest applications become so sluggish intermittently and there are no real ways to troubleshoot and resolve the problem it is impossible to get client buy-in and erodes hard earned trust. Can we get some type of formal response from Knack on what specifically is being done to address this?
The link now just directs to the what’s new page. You still haven’t fixed the date filter issues which you broke in the update and is still affecting most of my apps. That was an issue on that list which appears to have been quietly shuffled away.
Hi Kevin - we released some fixes related to date filter issues on November 30th which addressed a host of different issues.
Have you already submitted a support ticket with details on those to us at email@example.com?
If so, could you provide us with the ticket number so that we could track down the request and see if the issues you’re mentioning were tied to the November 30th fixes or is that a distinct issue still being worked on.
If you haven’t submitted a ticket with details on the issue, would you kindly do so?
We’ll circle back to you regarding the performance upgrade page redirecting to the what’s new page as soon as we confirm a few things internally.
Hi @Kevin , just wanted to circle back here regarding the performance issues page redirecting to the what’s new page.
To be fully transparent here - we have opted to redirect from this page to the what’s new page simply because this page was not being updated with any reasonable frequency, and hence it was not serving its purpose as a source of truth regarding what we’re working on and what we’re fixing.
We have since pivoted to a different approach to communicate those issues and updates, highlighting them in other channels, like these forums, via posts such as the below examples:
Hopefully, this provides you some more insight on this, and an idea of where to see relevant updates.
As far as the date filter issues go - as mentioned previously, if those persist despite the November fixes if you could kindly contact support that’d be much appreciated.