I have received some odd behaviour with a list workflow. The list and the workflow were created in SharePoint/Nintex workflow 2010 and all was working fine for a couple of years. The list and the workflow were then migrated to SharePoint/Nintex Workflow 2013 now whenever an item is added to the list (which meets the conditions for starting) two instances of the workflow start. I then amended the workflow to make it start when an item is created and added a"wait for item update" action to the start of the workflow which is set to wait for the value that was in the conditional start. When I create a new list item now only one instance of the workflow is started.
I have a solution to the problem but I would like to understand why the conditional start appears to be working incorrectly as it is possible that we have other workflow with the same problem. Does anyone have any ideas?