Get a retained Topic Memory processing block
Return one exact block, including its original diagnostics and any accepted retry, after recovery.
Authorization
BearerAuth Bearer credential resolved to an opaque authenticated Principal by the Server deployment.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/topic-memory/processing/blocks/get" \ -H "Content-Type: application/json" \ -d '{ "scope_id": "string", "block_id": "string" }'{ "block_id": "string", "attempt_id": "string", "scope_id": "string", "binding_name": "string", "source_after": 0, "source_through": 1, "budget_source_through": 1, "legacy_source_through": 1, "target_source_through": 1, "attempts": 1, "requests": 0, "tokens": 0, "error_code": "string", "last_error_code": "string", "blocked_at": "2019-08-24T14:15:22Z", "retried_at": "2019-08-24T14:15:22Z", "retry_request_generation": 1}Inspect Topic Memory processing and its current terminal block POST
Return the current Cursor, Source head, retained target and durable blocked-window diagnostics. An active final attempt remains pending because it may still finish. Legacy blocks receive their first observation timestamp; an unavailable historical error code is null. This operation never grants new processing allowance.
Explicitly retry one observed Topic Memory block POST
Require scope.admin and the exact block_id returned by status. Atomically retain the block's failure and usage evidence, grant one fresh bounded allowance and request asynchronous processing without advancing the Cursor or discarding the target or Sources. Repeating a block_id returns its original acceptance and cannot reset a later attempt. An unretried block that no longer owns the frontier returns topic_memory_block_conflict. Ordinary flushes, status reads, restarts and model changes never reset allowance.

