Hey guys! How are you!?
Recently, I started noticing that in some cases, when I update a plugin to a newer version and, for some reason, that new version stops working (either because it requires additional adjustments or because an element used by the plugin was replaced), the production version (live version), even without any deployment, is no longer able to load any configuration or workflow related to the updated plugin.
In this specific case, I updated the WASABI CLOUD STORAGE plugin to the latest version. The element that we place on the stage was replaced in this new version, and because of that, I now need to update multiple parts of my application, which ended up completely broken since the workflows were associated with an object that no longer exists (all workflows and conditions simply disappeared). And since the workflows and conditions simply disappeared, I completely lost track of where I would need to look, analyze, and update things.
My idea was to switch the app view to the live version (which had not been updated and was still running the older version of the plugin) to check how the workflows were originally built using the old plugin version, so I could reconstruct them.
To my surprise, the workflows simply do not load, even though the plugin is still on its old version in production.
I believe this may be a bug. The live version of my app is still holding the old version of the plugin, untouched and working. Therefore, the workflows should reflect the current state of that version. However, for some reason, that is not what is happening.
Anyway, I just wanted to make this post to bring attention to this issue.