`node-red-contrib-persistent-fsm` state does not persist on deploy

[Rudi3]

I'm not sure if the state is really supposed to persist on deploy (or if persistence applies to something else), but the name and the setting seem to imply that.
However, the state is always reset to initial state when deploying a flow (Even when "Persist state on re-deploy" is checked).
Is that unexpected behaviour for node-red-contrib-persistent-fsm?

I read that it's possible to use filesystem-based storage to save states - but would that really be necessary to persist when deploying?
I'd figure that would only be needed when restarting/shutting down node-red or the whole server?

I wanted to check if node-red-contrib-reboot-persistent-fsm solves this issue, but it looks like the package node-red-contrib-persistent-fsm can't be removed from the palette - (without editing some config files...).

---

Version: 20.0.0

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[Rudi3]

It's still an issue, I think.