The timeout execution parameter
specifies the amount of time in seconds that each analysis waits to receive the
co-simulation message expected from the other analysis that is running. The
default timeout value is 60 minutes.
When the timeout period is large compared to typical analysis increment
wallclock times, you have greater flexibility in starting jobs and performing
operations that precede the co-simulation analysis step. Examples where this
flexibility is needed include: job submission using queues, analyses where
steps that precede the co-simulation step have long run times, and cases where
one job is resubmitted because of an input error. However, a large timeout
period can cause problems when one of the co-simulation jobs fails (for reasons
such as convergence issues or availability of computer resources) before the
initial co-simulation communication is established. In these cases you may
prefer to terminate the job left running rather than have it wait the entire
timeout period.