First of all, congratulations on the new release! It looks fantastic, and I really appreciate all the improvements youāve made.
However, Iāve encountered a bug with the AI feature in the editor. Every time I use it, the changes are applied as expected, but the loading overlay with the spinner never disappears. To continue working, I have to manually reload the editor after each AI prompt.
If I donāt reload and just wait for the spinner to disappear, I eventually get logged out after a few minutes.
Is this a known issue, or is there anything I can do to fix it on my end?
As a broad comment @Raphael, IMO you really shouldnāt release something that replaces a functioning product, call it beta, have it be very buggy, and charge people for it! If this really is a beta (as it certainly feels like), then this should have been released separately to the stable version 2 for much more thorough testing, while production users continued to use version 2.
Iāll reach out separately to give you more tokens for these errors.
We are doing lots of optimizations as we speak + weāll make sure not to count for the tokens that led into errors very shortly.
Thanks for the feedback, we thought about it but unfortunately this was not technically achievable to have two versions of the ācopilotā acting together in the editor. We are improving it very quickly and making sure to cover for regressions, everything should feel much more stable in 2 to 3 weeks. Apologies for the disrupted experience in the meantime
Hi Raphael! The ai formula editor is simply broken now. I canāt even reference variables and it wonāt output anything. Plus the previous implementation was much better in terms of UX.
Hey! Yes agreed, there is a regression here, we are on it, we should push a fix in production next week and the experience should be as good (hopefully better) as before for formula management.
Following up here for anyone else who gets this issue. Not sure why the update caused the change, but the fix support was able to give me is to set the z-index on the dialog box.
In 2 - 3 weeks it will feel āmuch more stableā?? How can you release a new feature in production without an opt out possibility and just leave users with something completely unusable and unstable for weeks?
Better to revert the deploy, thoroughly test it and then release it again in my opinion. Especially for new users starting to use your platform, they will immediately go to other tools? Weāre locked in already.
Did you change something last minute before releasing 3.0? When we were testing in the closed beta it seemed to be working much better in my experience.
We are just talking about the AI usage, the rest of the platform is stable and as is (minus a few minor bugs that didnāt show up during the private beta and that we are fixing on the fly). Feedback from new users has been tremendous so far, our activation is through the roof. Let us know if there is any major instability and weāll fix it right away.
Giving access to a new feature to everyone in the production env always surfaces unseen issues that have a domino effect on others, things should start feeling better soon with the AI features.
Thanks @Raphael I appreciate it. I know you guys are doing your best. Itās just very frustrating when you hit continual errors and you are trying to make updates to a production application.
Hi @Raphael and @Alexis and @luka and @ishika. Once again, congrats on the launch, and I am happy to hear Raphael say āactivation is through the roofā. I am really proud of what you guys are building with weweb. Well done. BUT I must caution that new customers being pleased while hurting stable existing projects is not ideal AT ALL. If I am a proven customer with years of loyalty, I donāt wanna see my own projectās viability being hurt by an attempt to please new customers.
Now to my MAJOR ISSUE.
The Weweb 3.0 launch (AGAIN BROKE MASSIVE AMOUNTS OF WORKFLOWS) by removing the workflow trigger called āOn Mountedā. WHY?
So here is the situation. Before, in Weweb 2.0 there used to be a workflow trigger called āOn Mountedā for every single element, which fired when the element was added to the DOM and was useful for performing element side-effects. Now, it is no longer there. WHY?? LIKE WHY??? This is a standard Vue Lifecycle Hook as far as we know and I cannot understand why it has been removed without anyone even asking.
I have CRITICAL project flows that rely on that and I can see it was removed from the editor, but the underlying code still exists cos itās not breaking in my production apps (which I HAVE NOW REFUSED TO UPDATE cos I donāt know exactly what else has changed), it just precludes new use. Communicating what will change and soliciting feedback is key to long-term stability. If you are just going to change things without even telling us what exactly is going to change, then I may not have found my platform of choice as I had thought. Cos this is actually very very very annoying. Now I am wondering what else have you guys changed, and when will it show up as a production bug. The changes are NOT EVEN IN YOUR CHANGELOG! IF YOUR PLATFORM WORKS A CERTAIN WAY, it is annoying, very annoying, to whimsically have it begin working another way without even telling anyone. How many hours do you want your creators to spend just fixing bugs after each āupdateā. And this is NOT your first time of doing this. Itās annoying!
Do you guys realize people are building CRITICAL stuff on your platform?? Apologies if my message comes off as rude. Itās 3am and I am upset. Please can it be returned? Or is there at least a good reason it was removed?? Thanks
It looks fantastic, and I really appreciate all the improvements youāve made.
Iāll reach out separately to give you more tokens for these errors.