Please provide feedback based on my linked answers questions.
It applies to both schedule and condition starting rules. Instances will not be queued.
I just want to confirm something regarding the SINGLE INSTANCE MODE.
It reads it will wait for a "specific schedule workflow to run at a time" so doe this mean it only applies to Workflows with a SCHEDULE STARTING RULE? That seems to be the case as I tried it with a "ENTRY CREATED" Starting Rule and it does not seem to apply.
So through much testing it seems that SINGLE INSTANCE MODE works like this.
Workflows initiates, if the same Workflow tries to initiate it ignors and never runs it.
Workflow Instance 1 Initiates
Workflow Instance 2 Starts (Instance 1 is still running)
Instance 2 is ignored and never runs.
I was hoping that the following would occur.
Workflow Instance 1 Starts
Workflow Instance 2 Starts (Instance 1 is running) que Instance 2
Run Instance 2 once Instance 1 completes.
Okay yes that confirms what I have been testing.
Any possibilities for a change in the future essentially what I and based on research others have tried to accomplish is a Workflow that Runs continuously or sequentially:
1. As a Service
2. Single Instance Mode with Queueing.
I am continuously monitoring a folder for new documents, which may contain duplicates. I want to ensure I run every single document sequentially.
1. On Creation Single Instance Mode does not work as if multiple documents come in via Import Agent at the exact same time it will only kick off once.
2. Using Folder Document Count > 0 in a Wait for Entry Change then an Invoke Workflow on itself but is limited to 32 Iterations.
3. Schedule with For Each Entry does Work but incurs a time delay we were hoping to have documents processed real time.