I had once a case like that, when somehow my API call got outdated without me even touching it. And later I couldn’t recall it due to some issues. But I would guess it may be related to some api call if you are sure - you have not deleted any field in the db, deleted option set etc.
Check one and do the investigation - what is particaullary going on.
Maybe a plugin died?
if you’ve just run “cleanup app” then that creates a lot of issues in the checker because things are confirmed as deleted and so then most (not all) arguments that reference those things error - whereas when you just soft delete them in the backend they still exist and are just “hidden”
although “cleanup app” doesn’t delete them either - it just hides them from the editor
Hard to say. I haven’t used HTML headers that much. But in general - if you check errors one by one, don’t you see some patter like a value x is missing? Maybe you cna switch to live version and compare this error to what is on live - what value is missing, what has changed etc. Then you will grasp the logic what might have happened.
Realy hard to say. I checked few and “Reveal element” doesn’t show element that suppose to be in error.
It looks like invented elements or they changed sometihng and I got old deleted elements back in app…
So now I should manualy go through 158 elements and delete one by one… ?
See above - I discovered that workflows from other elements are now within index page workflows and they obviously don’t work. I did not put them there. It seems to be some system works not performed correctly!
Same situation on my end. I had around 30 errors suddenly appear this morning, while everything was working fine yesterday. I’ve already fixed most of them, and still have 11 left to tackle.
I’m posting here as the context of my issue seems very similar to what @atrium.celje described. Of course, if it turns out to be unrelated, I’ll move it to a separate thread.
What’s odd is that many of the errors are related to missing event names — which seems strange, since I’m quite sure I must have defined them if they were required. I wouldn’t have been able to deploy to production otherwise:
Also, as shown below, Bubble now throws an error where it expects a PatientReviewsCampaign thing, even though that’s exactly what was previously provided (PatientReviewsCampaign now). That reference has inexplicably become invalid. It’s easy enough to fix, but it’s concerning to see errors appear like this without any change from my side:
I noticed this when I toggled the new workflow editor on and off - it caused errors in the workflows I built in the new editor when I rolled back to the old editor - not sure if it is still the case
I also used new view of workflows. I now changed back to old one but the errors remain.
What I noticed is that I have (among others) in my index page workflows also other elements like from reusable elements.
Have you tried rollback? Does it help?
It is ob bugs list.
I just noticed that I can not switch back to old way of viewing workflows. Is that intentional?
I find old vesrion’s way of deleting unusable workflows easier / quicker..
That roll out is likely the cause of the bugs. I am experiencing it now too today.
Please ask team to fix this with urgency. I’m unable to work with this bug as it affects so many areas with data…it would just be a game of whack a mole if I were to try and resolve all on my own.