Skip to main content
POST
Retry a mass write operation
The operation must be done and have failed points. An operation that was cut off with points that never got an outcome also qualifies. Those points are marked FAILED with the code TIMEOUT and sent again. Points that failed with NOT_IN_PLAN are not sent again. The operation goes back to RUNNING, and metadata.retries goes up by one. Poll it as you did after the apply. An operation you do not read stays RUNNING and blocks the next mass write in its buildings.
The call returns 400 while the operation is not done, when no failed point can be sent again, or while another mass write is running in the same buildings.

Authorizations

Authorization
string
header
required

Paste an access token from Create an access token. Tokens expire, so request a new one if you receive 401.

Path Parameters

operationId
string
required

Identifier of the operation.

Pattern: [^\p{C}\p{Z}]{1,128}

Query Parameters

fields
string

Comma-separated top-level fields to return. One or more of name, done, metadata, response, and error. The default is every field. An unknown name returns 400.

Response

The operation, running again. The response is the operation itself.

name
string

Resource name of the operation. The last segment is the operationId.

Example:

"mass-write/operations/6acf8bcf8564cb8ad4ccf8f3"

done
boolean

Whether the operation has finished.

metadata
object

Progress and identifying data. Always present.

response
object

Outcome counts. Present when the state is SUCCEEDED.

error
object

Present when the state is FAILED.