Closing contingencies

Initially, the status of each contingency is set to "Pending". While the status is pending, the contingency is considered to be open.

A contingency can be closed either by resolving it or by waiving it. You can both resolve and waive contingencies through Cloud API. Except for the endpoint paths and the final status of the contingency, the behaviors of the two operations are the same.

Resolving contingencies

To resolve a contingency, use one of the following endpoints as appropriate:

  • POST /jobs​/{jobId}​/contingencies​/{contingencyId}​/resolve
  • POST /policies​/{policyId}​/contingencies​/{contingencyId}​/resolve

The /resolve endpoints do not require a request body.

When you resolve a contingency:

  • status is set to "Resolved".
  • closedDate is set to the current time.
  • closedUser is set to the API call's session user.

For more information on how the session user is determined, see the Cloud API Developer Guide.

Waiving contingencies

To waive a contingency, use one of the following endpoints as appropriate:

  • POST /jobs​/{jobId}​/contingencies​/{contingencyId}​/waive
  • POST /policies​/{policyId}​/contingencies​/{contingencyId}​/waive

The /waive endpoints do not require a request body.

When you waive a contingency:

  • status is set to "Waived".
  • closedDate is set to the current time.
  • closedUser is set to the API call's session user.

For more information on how the session user is determined, see the Cloud API Developer Guide.