Add time to internal clockAdded in 8.11 Physical tenant

POST 
/clock/add

Strongly Consistent About endpoint data consistency

Moves the Zeebe engine's internal clock forward or backward by the given offset. Unlike pinning, the clock keeps ticking in real time after the offset is added. If the clock is pinned, it stays pinned and moves to the pinned time plus the offset.

Each request adds to the time of the clock, so adding PT1H twice moves the clock two hours ahead. Use POST /v2/clock/reset to remove all added time and return the clock to the system time.

The response contains the new time of the clock. The change reaches all partitions shortly after it is accepted, so a request sent right after it may still use the previous time.

Required permissions

When authorization is enabled, this endpoint requires the following permission. See resources and permissions to learn more.

Resource type	Permission
SYSTEM	UPDATE

Request

Responses

200

The time was added to the clock.

400

The provided data is not valid.

401

The request lacks valid authentication credentials.

Response Headers

WWW-Authenticate

403

Forbidden. The request is not allowed.

500

An internal error occurred while processing the request.

503

The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains RESOURCE_EXHAUSTED. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .