Work Request Status

Describes the various statuses applicable for a load balancer's work requests.

Many of the Oracle Cloud Infrastructure Load Balancing service requests do not take effect immediately. In these cases, the request spawns an asynchronous workflow for fulfillment. To provide visibility for in-progress workflows, the Load Balancing service creates a work request object.

Because some operations depend on the completion of other operations, you must monitor each operation’s work request and confirm it has succeeded before proceeding to the next operation. For example, if you want to create a backend set  and add a backend server to the new set, you first must create the backend set. After that operation completes, you can add the backend server. If you try to add a backend server before the backend set creation completes, the system cannot ensure that the request to add the server succeeds.

You can monitor the request to add a backend set to determine when that workflow is complete, and then add the backend server.

The following table lists the work request states:

Status

Description

Accepted

The request is in the work request queue to be processed.

In Progress

A work request record exists for the specified request, but no associated WORK_COMPLETED record exists.

Succeeded

A work request record exists for this request and an associated WORK_COMPLETED record has the state Succeeded.

Failed

A work request record exists for this request and an associated WORK_COMPLETED record has the state Failed.

Check the Error Details column for more information on the reason for the fail. For example:

All five non-reserved IP addresses of the subnet_CIDR for ocid have already been allocated.