Hello Guys,
Just checking if this is a farmiliar scenario, do specific Nintex Actions become invalidated after workflows are re-published.
I have observed this with some of the actions with conditions eg loops, query lists, where the conditions are not visible on the action configuration settings when re-opened, but a mouse over the action shows the configured conditions correctly in the label. Are there any browser issues related here?
I had a regular expression configured a while back which all worked fine but only applied in specific scenarios, some updates have been made on the workflow over time but no updates on the regular expression.
Recently, I had this scenario where the regular expression was applicable but it didnt seem to perform its function, I ran tests logging the specific variable in workflow history and this proved that the function did not work. I then added a new regular expression with the same configuration, disabling the old one, and everything seemed to work again as expected.
Are the any explanations for this behaviour? Why would a configured action become invalidated?
Adeboye