Edgio

Multipart State Codes

Both multipart uploads and multipart pieces have lifecycles along with states that indicate where they are within their lifecycle. Each state has an associated integer code and a status string.
State codes for mutlpart uploads are visible in the output from calls to getMultipartStatus and listMultipart (see Get Status for a Multipart Upload and List Your Multipart Uploads).
State codes for mulipart pieces are visible in the output from calls to listMultipartPiece (see List Pieces in a Multipart Upload).
You can programmatically obtain the status strings by calling getMultipartStatusMap (see Get String Equivalents of Multipart Status Codes). This makes it easy to obtain status strings at runtime.
Allowable state transitions are listed in Multipart State Transitions.

Multipart Upload State Codes

The following table shows the status string and description for each code.
CodeStatus StringDescription
0UNKOWNImpossible state
1NEWJust created and contains no pieces
2READYOne or more pieces have been added. Ready to be completed.
3COMPLETEMultipart upload has been completed
5JOINJoin in progress. (The pieces are being joined in order to create the final file.)
6SUCCESSJoin completed and the final file has been created on disk.
8DELETEDPieces have been deleted from all s
9ERRORAn internal error occurred
10ABORTAborted by user
11EXPIREDWhen a multipart upload that is in NEW or FAILED state reaches an age older than a defined amount of time, the upload is transitioned to EXPIRED state if all associated pieces are also in EXPIRED state.

The age limit defaults to 1 day. Contact your Accouont Manager if you want to disable the expiration of aged multipart uploads, or if you want to set the expiry to other than the default.
12FAILEDAn error occurred during the merge process, such as a 404 or a checksum error.

Multipart Piece State Codes

The following table shows the status string and description for each code.
CodeStatus StringDescription
0UNKOWNImpossible state
1NEWPiece has been added to a multipart upload.
5JOINPiece is being joined (merged) to a multipart upload.
6SUCCESSPiece successfully joined
8DELETEDPiece successfully deleted from all s
9ERRORAn internal error occurred
10SKIPPEDA piece enters SKIPPED state if it is located outside of the local domains on which LLPs run.
11ABORTAborted by user
12EXPIREDWhen a multipart piece that is in NEW or FAILED state reaches an age older than a defined amount of time, the piece is automatically transitioned to EXPIRED state.

The age limit defaults to 1 day. Contact your Account Manager if you want to disable the automatic expiration of aged multipart uploads, or if you want to set the expiry to other than the default.
13FAILEDPiece error; example: piece not found