Retry a mass write operation
Sends the failed points of an operation again. The operation runs again under the same id.
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.
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
Paste an access token from Create an access token. Tokens expire, so request a new one if you receive 401.
Path Parameters
Identifier of the operation.
[^\p{C}\p{Z}]{1,128}Query Parameters
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.
Resource name of the operation. The last segment is the operationId.
"mass-write/operations/6acf8bcf8564cb8ad4ccf8f3"
Whether the operation has finished.
Progress and identifying data. Always present.
Outcome counts. Present when the state is SUCCEEDED.
Present when the state is FAILED.

