Synchronizing a RouteCloud Scenario with Verizon Connect Fleet
- Authentication required.
- Request body: sync_request.
- Response body:
wait=1specified, returns the task result (see below).
- Otherwise, returns a task_redirect_response.
- Task result:
This endpoint is used to publish changes made in a RouteCloud Scenario to live data.
If changes have been made to the live data since your scenario was created, your changes may not be published. This can occur if your changes were based on out-of-date information or conflict with other changes made. To check for unpublished changes inspect the sync_response. In this situation we suggest you request a fresh snapshot and repeat the operation.
wait=1- Optional. Wait until the
buildcompletes before returning the result. See Asynchronous vs Synchronous.
wait=1was provided and the
buildresult is not yet available, a redirect is sent every 15 seconds (instead of a normal result) to refresh the HTTP timeout. See Asynchronous vs Synchronous.
400- The request was invalid. The response will be an error_response.
401- Authentication required.
|string||commit_local||Must be set to "when_no_conflicts"|
|string||sandbox_id||The id of the sandbox to publish|
|boolean||publish_all_job_assignments||Should be set to true to apply the job assignments you have made in your scenario|
|delta||local_changes||Lists any changes that were not applied. Changes might not be applied if another user has modified the live data (which can lead to a conflict) since your scenario was created.|