Publish an older version without rolling back the Editor?

Hi there!

First of all thank you so much to the time for the versions which can be viewed in the editor as “Backup”. Recently had the opportunity to copy an element from an old version and paste it into my current live editor - that felt fantastic!

However I am now facing a bit of an obscure issue. My deployed app freezes for 40-50 seconds, and Devtools Network (or other devtools) are useless because they also freeze and record nothing during that time. I have for habit to publish my changes multiples time before exploring my deployment more in depth, mostly to save time. As such, I know for sure that rolling back to the most recent version will not fix the issue - and I do not know when I introduced the bug.

Would it be possible for me to publish a previous commit (or deployment?) without rollback?
E.g.: Publish a December 30th commit, check if problem is present in deployed app. Yes still present. Publish December 29th commit, check if problem present. Not present → check the logs to see what I did, to narrow down the problem etc…

Many thanks in advance for your assistance.

Hey @aeynaud :wave:

This is not possible at the moment, but this is a nice idea. Could you file it on feedback.weweb.io? We’ll add it to our roadmap.

Such loading issues are often due to sluggish workflows. Did you try launching the editor in safe mode?

Thanks @Quentin , added a feedback ticket!

This might take some time, but would it still be safe for me to rollback, publish, check, rollback, publish etc… ? Safe mode doesn’t really help as the problem only ever exists in the deployed/published app.