Retrieves all Runs for the specified connection.
Notes
The Prefer
header can be used to specify how much result metadata is desired by the client. The Prefer
request header field is used to indicate that particular server behaviors are preferred by the client but are not required for successful completion of the request.
This operation supports "return=representation"
and "return=minimal"
preferences.
The "return=representation"
preference indicates that the client prefers that the server include an entity representing the current state of the resource in the response to a successful request.
The "return=minimal"
preference indicates that the client wishes the server to return only a minimal response to a successful request. This is the default preference if Prefer
header is not specified.
Authentication
Requires Authorization
header with valid Bearer token for scope itwin-platform
.
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
Request parameters
Request headers
OAuth access token with itwin-platform
scope
Setting to application/vnd.bentley.itwin-platform.v1+json
is recommended.
Response 200 OK
OK
{ "runs": [{ "id": "a1ecbdc8c4f6173004f9f881914a57c5511a362b", "state": "Completed", "result": "PartialSuccess" }], "_links": { "self": { "href": "https://api.bentley.com/synchronization/imodels/connection/{connectionId}/runs?$skip=100&$top=100" }, "prev": { "href": "https://api.bentley.com/synchronization/imodels/connection/{connectionId}/runs?$skip=0&$top=100" }, "next": { "href": "https://api.bentley.com/synchronization/imodels/connection/{connectionId}/runs?$skip=200&$top=100" } } }
Response 401 Unauthorized
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
{ "error": { "code": "HeaderNotFound", "message": "Header Authorization was not found in the request. Access denied." } }
Response 404 Not Found
This response indicates that the specified connection not found.
{ "error": { "code": "StorageConnectionNotFound", "message": "Requested StorageConnection is not available." } }
Response 422 Unprocessable Entity
Invalid request to get connection.
{ "error": { "code": "InvalidStorageConnectionRunsRequest", "message": "Cannot perform operation.", "details": [{ "code": "InvalidValue", "message": "Page size is out of limits.", "target": "$top" }, { "code": "InvalidValue", "message": "Provided connectionId value is not valid.", "target": "connectionId" } ] } }
Response 429 Too many requests
This response indicates that the user has sent too many requests in a given amount of time.
{ "error": { "code": "TooManyRequests", "message": "More requests were received than the subscription rate-limit allows." } }
Response headers
The number of requests exceeds the rate-limit for the client subscription.
Runs (prefer return=minimal)
Run error details
Error key.
More information about run error.
Runs (prefer return=representation)
storage-run
A connection run id.
Connection id.
A timestamp when connection run started.
A timestamp when connection run ended.
storage-job
A storage job id.
A timestamp when storage job started.
A timestamp when storage job ended.
A string indicating current execution status of the job.
A string indicating outcome of the executed job.
Type of connector used for synchronization. Refer supported connector format for details.
storage-task
A storage task id.
A timestamp when storage task started.
A timestamp when storage task ended.
The number of attempts when storage task was retried.
Storage file id.
A string indicating current status of the storage task.
A string indicating outcome of the storage task.
Job Phase
One of 'Preprocessor', 'MasterFile', 'ReferenceFile'.
Execution State
One of 'NotStarted', 'Idle', 'WaitingToExecute', 'WaitingToRetry', 'Executing', 'Finalizing', 'Completed', 'Queued'.
Execution Result
One of 'Undetermined', 'Success', 'Error', 'PartialSuccess', 'Skipped', 'Canceled', 'TimedOut'.
Run (summary)
A run id.
A string indicating current status of the run.
A string indicating outcome of the run.
task-error
Error code.
A human-readable representation of the error.
More specific information about the error.
An integer representing connector exit code.
System.
Phase.
Category.
Description key.
Description.
A link to public documentation for known errors.
A boolean value representing if the error is user fixable or not.
Task details
Synchronization report
Error message explaining the result
Number of errors in the report
Number of warnings in the report
Number of other issues in the report
Suggested action
Error severity level
Link
Hyperlink to the specific entity.
Links (paging)
URLs for redoing the current request, getting to the previous or next page of results.
Connector type
One of 'AUTOPLANT', 'CIVIL', 'CIVIL3D', 'DWG', 'GEOSPATIAL', 'IFC', 'MSTN', 'NWD', 'OBD', 'OPENTOWER', 'REVIT', 'SPPID', 'SPXREVIEW'. Name of the Connector that is used for synchronization.
Error
Contains error information.
One of a server-defined set of error codes.
A human-readable representation of the error.
The target of the error.
Error Response
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.