Skip to main content

getCascadeProgress

MetadataOperationWrapper getCascadeProgress(folderId)

GET /api/2.0/files/metadata/folder/{folderId}/templates/progress

Get cascade progress

Reports the cascade pass of a folder started by PUT api/2.0/files/metadata/folder/{folderId}/templates: the running one, otherwise the most recent one. The caller needs read access to the folder, the call is read-only. progress is the share of the subtree processed, isCompleted tells the pass is over and error carries the reason of a failed one; a completed pass without an error has written every template and value it was asked for. A folder that never cascaded, or whose passes were already dropped, is answered with a completed operation without an identifier rather than with an error. A folder that does not exist is answered with 404.

Parameters​

NameInTypeDescriptionNotes
folderIdpathInteger (int32)The folder the operation acts on. Take the identifier from a listing such as GET api/2.0/files/@root or GET api/2.0/files/{folderId}: a folder stored in the portal is numbered, while a folder in a connected third-party account is named by an opaque string.[required] [example: 1]

Responses​

Status codeDescriptionTypeResponse headers
200Cascade operation status; a completed operation without an ID when the folder has no cascade to reportMetadataOperationWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
404Folder not found--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
400Bad Request.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

MetadataOperationWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: Not defined
  • Accept: application/json