Hi momlo, thanks for the reply.
Yes, it seems like it is just one session. As I mentioned, the "Main" flow finishes after the subsidiary flow that is selected through the IF statement in the main flow.
So, the timing goes like the following:
Cloud flow is scheduled to run every minute with maximum concurrent runs set to 1 so that it is only running 1 at a time.
When the cloud flow starts, it is running the "Main" desktop flow.
The "Main" desktop flow shows "running" in the desktop flow monitor fairly quickly.
The "Main" desktop flow is 60 lines, but basically retrieves a file, looks at the file name and then, using the file name, has a 20 part "if file name A".... "Run desktop flow A"..... "else if file name B".... "Run desktop flow B"...."else if file name C".... "Run desktop flow C".... END
The desktop flow monitor shows about 3.5-4 minutes at the time that I see the subsidiary flow selected in the main flow kick off on the machine.
The subsidiary flow runs as it should for about 1 minute on the machine and shows as "running" in the desktop flow monitor.
The subsidiary flow concludes and then, shows success in the desktop flow monitor.
The main flow still shows "running" in the desktop monitor, but it also concludes soon after (within 10 seconds) and shows success in the desktop flow monitoring.
I don't think the Main flow is large with only 60 lines and our network is not normally slow in any way, it is on a fiber internet connection. I also run some recurring cloud flows triggering single desktop flows that don't have the "IF" "ELSE IF" subsidiary desktop flow logic and those flows trigger and complete in less than a minute, so it seems like maybe it is related to the subsidiary flow setup.
Is there any way to better determine where the timing issue is?
