Advance a test clock
Requests forward-only asynchronous advancement. Ionic processes every
intervening billing action in chronological order and returns the
clock in advancing state. Poll retrieval until it becomes ready.
A busy clock rejects a different overlapping request. If a clock is
failed, resolve the reported issue and request its retained target
again with a new idempotency key; Ionic resumes after the last committed
checkpoint. A failed clock rejects a different target.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Unique key used to replay this mutation safely.
1 - 255Connected Ionic account to operate when using an authorized platform credential. Omit when using the account's own credential.
Path Parameters
Test clock ID.
^tclk_[0-9A-Za-z]{14}$Body
Strictly later logical time as Unix epoch seconds, no more than two calendar years after the current frozen time.
1 <= x <= 253402300799Response
The clock accepted for asynchronous advancement.
^tclk_[0-9A-Za-z]{14}$test_clock ready means all billing work through frozen_time committed.
advancing means ordered work remains before target_time.
failed means processing stopped at the last committed checkpoint.
ready, advancing, failed Last fully committed logical checkpoint.
Requested destination while advancing or failed.

