14 to 15 minute delay between activation and start time

[John B]

A flow with no configured time delays does not start for extended periods of time.  How would I eliminate this delay?  Thanks.

[Cristian Suciu]

Have you tried bouncing the remote agent on which the job is running? 

We had a similar issue recently where all the jobs running on the same agent had a runtime of aprox. 6 minutes and 40 seconds, jobs that before were running in 2-3 seconds. We saw in the job reports time outs and traces with TLS handshake message in them. I bounced the Unix agent and jobs started running normally after that.

Additionally, is this flow the only one experiencing this behavior? It might also be due to a time difference on the server where the agent or AE are installed. 

[Andrzej Golaszewski]

Hello John B,

some more information could helpful to give you an appropriate answer.

1. Which AE Version is in use?
2.  There are different Execution stages for workflow an jobs. Do The Workflow stuck in an execution stage?
3. Does the workflow stuck or only the starttime of the first job.
4. There are some references to this behavior in the log files of AE (WP's, CP's)? Messages in Workflow/Job Logfiles could be helpful too. 
5. Is this behavior everywhere or only on one Agent?
6. Does this behavior appears on every workflow?
7. Can you give an export of your workflow?

Hope the questions help to get an overview over the problem

-------------------------------------------

Best regards

Andrzej Golaszewski