No way @vladimir-upirov
Only I am doing changes and also you can see the IP address if you can from the location we are deploying.
Suppose if anyone is deploying, the changelog should show old changes as those are also not showing.
The scenario you described where the deployed code “is missing blocks” is technically not possible since the deployed code doesn’t have blocks. The only possibility is when someone changes the logic and then deploys it.
The changelog maintains the changes done on your computer only, it doesn’t have any changes made by anyone else. When the logic is deployed, it runs as code, not as codeless blocks. Even if the codeless logic in the form of blocks changes and is not deployed, the code that runs on the server is not impacted.
When you deploy and get a confirmation that the logic is deployed, you can reload the browser to make sure the logic looks exactly as what you had.
Regards,
Mark
@mark-piller Is there any way to track this?
Its happening only in one API. Which screenshot I sent you after that I canged that condition and now its again showing like I didn’t change anything.
Now I am changing it to below screen
and I am closing for the day now and no one will publish till tomorrow.
Can we check the same change on server tomorrow without deploying anything to server?
Try opening that logic in another browser or in Chrome’s incognito mode. Do you see any changes there?
Hi @mark-piller
Just checked now,
Icognito doesn’t show changes right now.
How this use case is possible?
- I have done changes
- Deployed
- QA team tested and its working
- After next day QA team said Its not working again
Same thing will be going to happen today now.
I believe it happens because of the “exceeded the quota” error with Browser LocalStorage, as you have shown here Deploying production to Dev enviornment - #10 by Baljeet_Singh
That’s why @Dima asked you to check your browser’s DevConsole to see any errors there Changes are getting undone automatically - #4 by Dima_Vak
The issue has been fixed and it is in the testing stage, we are planning to release it next week, while it’s not I can recommend you to clean up your local storage manually
Hi, @Baljeet_Singh
The issue is in testing, we are planning to release it this week. As soon as the fix is in production, we will let you know.
Regards,
Marina
Okay, Thanks.
@Marina.Kan Any update on this, please.
We are very stressed. Daily our changes are undoing automatically.
Hello @Baljeet_Singh
It is look like your localStorage is full.
In this release we have added functionality to help you avoid these problems. This is the Local Storage Cleaner. The following popup will appear if you have reached the local storage limit. This functionality will help display if any Backendless applications are storing data in local storage. This can be either UI-builder data or Codeless Business Logic data. It also has a function to clear Backendless data from the local storage.
https://monosnap.com/direct/vwSgNrA35yW7IxAEPr8uegOyQ63Vs9
If Local Storage Cleaner can’t help you, I recommend you do it manually.
Go to local storage in your browser, and delete every key from here ( screenshot ). ( You must be in the develop.backendless.com domain )
Don’t forget deploy your codeless logic if it not save
https://monosnap.com/direct/GOq4wKF9757R6BOCADYMLKs1k7IQ0B
Regard, Viktor
Can we manually open this popup?
No you can’t do it.
It only appears when the local storage is full.
In this popup you can clean only codeless keys.
I am guessing that your storage may be populated with other keys
Thats why I recomend you clean it manualy
Regard, Viktor
So, it has been resolved right now?
Your application has a lot of business logic (codeles methods, functions, timers, etc.), for any action with blocks in them, we store changes locally for different purposes - such as changelog, etc. Therefore, due to such a large amount of data as yours, it is impossible to avoid overflowing local storage. This popup will appear when you exceed the data storage limit, and it will help you clean it up quickly and easily.
We got the undone issue again in timers.
I have changed many times the time to 60 seconds and updated start date time of timer but after few minutes of updating, changes are undone from the timer.
bad issue, we are near to launch and stuck due ti these things failing. Please help on this ASAP.
Is issue still occurs?
As I can see, timer is redeployed and now should run every 60 seconds.
Regards,
Olha
Yes, not changed now.