I’m working on a flow and I’m experiencing weird behaviour. Sometimes, I make a bunch of changes, and I get feedback that I saved:
But if I close and reopen the Flow, It loads an older state. My most recent changes are gone.
I’m not sure if it’s because I’m still on the free plan, or if I hit some limit in terms of number of blocks / connections / etc.
It’s not because I was idle. I’ve done some tests now where I made the change, validated the auto-save, and then immediately closed and reopened the flow. 50/50 chance my last change isn’t there.
Postman for Windows 11.0.12. I remember seeing a prompt to upgrade in the morning. I upgraded, and then in the afternoon started to notice this issue.
We started using Postman a month ago, and did notice saving issues similar to how I described. But at the time we figured we were doing something wrong. When I posted yesterday, it was the first time I started paying attention, to determine root cause.
Flow ID 663163dfcaa10600319b012a
Other info which might be helpful
Free tier
Team workspace with 3 members
Flow originally created by one member, and I was making edits
Hi @atorrenosensei. I am the engineer looking into the issue. I can indeed confirm that one of tabs stuck in the older state has inadvertantly overridden the work.
We maintain a history of all changes being made to a flow, so I can observe a few times when this happened. I just wanted to assure you that none of the changes are lost if you see the Saved green tick, we can always recover to an previous state. (We are working towards making this feature also available to all our user).
The reproduction steps are really helpful, we will give you an update once we confirm the root-case and have a fix out for this issue. This is high-priority for us. Once again really sorry that you had to face this issue.
Hi @atorrenosensei , I was able to reproduce the issue based on your steps and I have fixed it internally. Currently testing for stability. However, getting the fix out requires us to push an update to the postman app. I will try and get it out as soon as possible. Thanks.
Hi @s-a-g-e, I am experiencing similar issues where I am losing Flow edits. Today I lost several hours work in Flow ID 664538550170570032e29a3e. This has happened to me on three occasions now, usually when I change machines or accounts. This time, I think it may glitched when I opened another account in the browser to reference api’s related to the work I was doing in the desktop app. Any help restoring the Flow to my latest changes would be greatly appreciated. It is getting to the point that I have such low confidence that my work won’t be yeeted at any time it’s becoming untenable to use the product.
Hi @wally.usq , I am really sorry that you faced this issue. I will definitely assist in the recovery.
This issue is happening because the Flow tab within postman is not closing and cleaning properly. So when you close the tab, even if the tab seems closed, the state of flow stays active, and in some unique situations this old stray flow writes over the current state. The fix has been applied to next release and the roll-out will start within the next 24 hours.
Meanwhile, as the issue is most prominent with the desktop app, I have one reccomendation. To prevent the loss until the fix is out, completely close the postman app if you close a flow tab. This will ensure that the stray flow doesn’t keep running in the background.
Within our internal dashboard I have identified the point where the data loss has happened.
I will go ahead and recover your flow to the state before that last update happend.
I know trust is hard earned, so I am going to update our roadmap to include the feature where you can view the entire history of changes. That way you can always be certain that there will never be any data loss and you can restore your flows in the worst case by yourself.
Hi @vetallace, We don’t have the feature yet in the app to rollback/restore by yourself. If you can share with me the id of the flow and the time to which you want to rollback or when you lost data, I will help you do it from the backend.
@wally.usq I have restored the flow for you. From your end, just to be safe, please quit the postman app completely and then open the flow. If everything looks good, give me a
Thanks so much @s-a-g-e! Very much appreciated and thanks for being so transparent and responsive. I just checked the flow and it looks like everything is restored correctly.
@atorrenosensei Yes, 11.1.14 that was released yesterday will have the fix. I would recommend all team memebers who use flows to upadate to this version.
