Please remove the Publish button. There are many bugs that prevent proper debugging of the tool. The previous mode was better; this button has several types of issues that make correct debugging in production mode impossible.
Hi @Erasmo_Lacerda ,
Can you please explain and give more information around what issues you are facing with reproducible steps.
I encountered a situation where unpublished changes in a workflow don’t take effect during production execution if a cron job is used. However, if an error trigger node is used, the production execution runs with the latest version of the workflow, even with unpublished changes.
To clarify:
When using a cron job trigger, the changes that I make in the workflow, but haven’t published, do not reflect in the production execution.
On the other hand, when using an error trigger node, even though the changes are not published, they are still used in the production execution.
This seems like an inconsistency in how the workflow versions are applied, depending on the trigger used. I’ve attached images showing both cases for further clarification.
Hey @George5867
Your case is worth reporting as it isn’t documented yet. Try to open a new GitHub issue with your reproduction steps and the screenshots you have.
In my opinion, as a workaround, don’t save unpublished changes if the error trigger workflow is active in production. The safest approach is to duplicate the workflow, make changes in the copy, test, then publish the original with the final version.
Hope will get fixed soon 