Get internal clockAdded in 8.11 Physical tenant

GET 
/clock

Strongly Consistent About endpoint data consistency

Returns the current time of the Zeebe engine's internal clock. If the clock is pinned, this is the pinned time. Otherwise, the clock ticks in real time and this is the engine's current time.

Use this endpoint to check the time that the engine uses, for example after pinning the clock with PUT /v2/clock, adding time with POST /v2/clock/add, or resetting it with POST /v2/clock/reset. A pin, add, or reset reaches all partitions shortly after it is accepted, so a request sent right after it may still return 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	READ

Responses

200

The current time of the clock.

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 .