DocumentProcessingOperation
Receipt for one accepted processing attempt. document_processing is first-time extraction of a stored document; reprocessing is a subsequent processing run. Poll GET /operations/{operationId}; the result references the document once this specific run completes. Atlas availability is checked separately. The receipt exposes the effective scrubPII policy; success requires any newly enabled scrubbing to complete before downstream processing.
New public operation abstraction over owner-specific asynchronous jobs. Success describes the documented live-data operation, not deletion of all backups or audit evidence. Holds and retained copies remain explicit. Reading requires the initiating integration and the operation-specific authority; erasure-status access is independently authorized after the identity is removed. Stored-document processing uses POST /documents/{documentId}/processing-runs.
- attemptType: integermin:1required
Accepted processing attempt; present for document processing operations.
- createdType: stringFormat: date-time
At requiredthe date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z
- documentType: string
Id min length:1requiredPresent for document_processing and reprocessing operations.
- failureType: stringnullable
Code required - idType: stringmin length:1max length:255required
- Properties: 2resultType: objectnullablerequired
- scrubType: boolean
P I I read-onlyrequiredEffective scrubbing policy for the accepted document-processing attempt. A queued receipt is not proof that scrubbing has completed.
- statusType: stringenumrequiredvaluesqueuedrunningsucceededfailedblockedcancelled
- typeType: "document_processing" or "reprocessing"enumrequired
- updatedType: stringFormat: date-time
At requiredthe date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z
- userType:
Id required - Properties: 3retainedType: array of object
Copies