Hi Oliver Lampl

if workflow number 2 have no conditional start and its "Magically" started, then i would recommend the following :

- on the document library click on the "workflow settings" .. this is on the main ribbon

- that should display the  SharePoint page of workflow settings for this Doc. Lib.

- it will be ideal in your situation to "Remove" all the instance on this Doc. Lib for these 2 workflows and start fresh. Is that possible?  .. Or just "Remove" the WF instance that you think they should not be there in the first place.

- Once you do that ... then try your test again.

The other scenario i'm thinking of is, would it be possible that the Workflow #2 is using a Content Type, and the Content Type  is associated with a Template workflow that have conditional start?

Hope that help.

Thanks

Majid

Hello Majid,

thank you for your replay, it is possible that your tips are related to Nintex Workflow on Premise?

For me it looks like

SharePoint online doesn't exists a versioning for workflows, even it isn't possible to configure an conditional start.

I recreated the hole DocLib (with one Content Type), but the problem still remains.

In the meanwhile I contacted the Nintex Support

br oli

Nintex support answer quick, and gave me the answer.

Here the answer:

Thank you for your e-mail.

This is a known bug in Nintex Workflow for O365.

Nintex Workflow for O365 allows you to untick all the start options which is a bug because you have to have at
least one start option.

If you try to do this in SharePoint
Designer you will get an error when you try to publish stating that you need to have at least one start option.

If you untick all start options and have another workflow start the workflow with not start options will also start.

The workaround is to tick the Manual start option on the workflow and re-publish.

Please let us know if you have any
questions.

Kind Regards