public StartSimulationJobBatchResult withStatus(String status) {
        setStatus(status);
        return this;
    }
<p>
The status of the simulation job batch.
</p>
<dl>
<dt>Pending</dt>
<dd>
<p>
The simulation job batch request is pending.
</p>
</dd>
<dt>InProgress</dt>
<dd>
<p>
The simulation job batch is in progress.
</p>
</dd>
<dt>Failed</dt>
<dd>
<p>
The simulation job batch failed. One or more simulation job requests could not be completed due to an internal
failure (like <code>InternalServiceError</code>). See <code>failureCode</code> and <code>failureReason</code> for
more information.
</p>
</dd>
<dt>Completed</dt>
<dd>
<p>
The simulation batch job completed. A batch is complete when (1) there are no pending simulation job requests in
the batch and none of the failed simulation job requests are due to <code>InternalServiceError</code> and (2)
when all created simulation jobs have reached a terminal state (for example, <code>Completed</code> or
<code>Failed</code>).
</p>
</dd>
<dt>Canceled</dt>
<dd>
<p>
The simulation batch job was cancelled.
</p>
</dd>
<dt>Canceling</dt>
<dd>
<p>
The simulation batch job is being cancelled.
</p>
</dd>
<dt>Completing</dt>
<dd>
<p>
The simulation batch job is completing.
</p>
</dd>
<dt>TimingOut</dt>
<dd>
<p>
The simulation job batch is timing out.
</p>
<p>
If a batch timing out, and there are pending requests that were failing due to an internal failure (like
<code>InternalServiceError</code>), the batch status will be <code>Failed</code>. If there are no such failing
request, the batch status will be <code>TimedOut</code>.
</p>
</dd>
<dt>TimedOut</dt>
<dd>
<p>
The simulation batch job timed out.
</p>
</dd>
</dl>

@param status
       The status of the simulation job batch.</p>
       <dl>
       <dt>Pending</dt>
       <dd>
       <p>
       The simulation job batch request is pending.
       </p>
       </dd>
       <dt>InProgress</dt>
       <dd>
       <p>
       The simulation job batch is in progress.
       </p>
       </dd>
       <dt>Failed</dt>
       <dd>
       <p>
       The simulation job batch failed. One or more simulation job requests could not be completed due to an
       internal failure (like <code>InternalServiceError</code>). See <code>failureCode</code> and
       <code>failureReason</code> for more information.
       </p>
       </dd>
       <dt>Completed</dt>
       <dd>
       <p>
       The simulation batch job completed. A batch is complete when (1) there are no pending simulation job
       requests in the batch and none of the failed simulation job requests are due to
       <code>InternalServiceError</code> and (2) when all created simulation jobs have reached a terminal state
       (for example, <code>Completed</code> or <code>Failed</code>).
       </p>
       </dd>
       <dt>Canceled</dt>
       <dd>
       <p>
       The simulation batch job was cancelled.
       </p>
       </dd>
       <dt>Canceling</dt>
       <dd>
       <p>
       The simulation batch job is being cancelled.
       </p>
       </dd>
       <dt>Completing</dt>
       <dd>
       <p>
       The simulation batch job is completing.
       </p>
       </dd>
       <dt>TimingOut</dt>
       <dd>
       <p>
       The simulation job batch is timing out.
       </p>
       <p>
       If a batch timing out, and there are pending requests that were failing due to an internal failure (like
       <code>InternalServiceError</code>), the batch status will be <code>Failed</code>. If there are no such
       failing request, the batch status will be <code>TimedOut</code>.
       </p>
       </dd>
       <dt>TimedOut</dt>
       <dd>
       <p>
       The simulation batch job timed out.
       </p>
       </dd>
@return Returns a reference to this object so that method calls can be chained together.
@see SimulationJobBatchStatus
aws-java-sdk-robomaker/src/main/java/com/amazonaws/services/robomaker/model/StartSimulationJobBatchResult.java