Skip to main content
request_check Queue one metered check: subject link rechecks a monitored placement (subjectId is the watch id), subject target rechecks a destination (subjectId is the target id). Reuse the idempotency key when retrying; blocked results remain unknown.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
Checks and monitoring can consume workspace capacity. Queued admission is not a completed observation; inspect the returned job or saved state.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

subject selects what is checked: link rechecks a monitored placement and subjectId is its watch id; target rechecks a destination and subjectId is its target id. The retired names request_link_check (watchId) and request_target_check (targetId) resolve here with the subject implied and the id renamed. Save the returned job identifier and read get_check_job. A queue response is not a completed observation. Replay the same idempotencyKey for the same intended check. An existing queued/running watch job returns WATCH_BUSY with its job_id; a completed attempt enforces a sixty-second cooldown before a new check. Save the returned job identifier and read get_target_job. Destination jobs and evidence are independent of source-link presence. Reuse the original idempotencyKey after a lost response. A paused or already-busy destination needs its current state inspected before new admission.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • id (string, required): Resource identifier returned by the operation.
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record. values: “queued”, “running”, “succeeded”, “failed”, “cancelled”
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • watch_id (string, optional): Identifier returned by the related operation.
  • target_id (string, optional): Identifier returned by the related operation.
  • type (string, optional).
  • execution_mode (string, optional).
  • idempotency_key (string, required): Caller retry identifier, bound to the original request arguments.
  • payload_hash (string, required).
  • attempt_count (number, required).
  • max_attempts (number, required).
  • lease_token (string / null, required).
  • lease_expires_at (string / null, required).
  • error_code (string / null, required): Latest delivery detail code; null when no failure or retry has been recorded.
  • error_message (string / null, optional).
  • created_at (string, required): UTC timestamp when the record was created.
  • updated_at (string, required): UTC timestamp of the last record update.
  • completed_at (string / null, required).
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
  • usage (object / null, optional).
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_check_job · get_history Follow the related workflow, inspect capability status, or return to the command index.