jobhunt.app/mcp

Retries, revisions and lost replies

Recover an uncertain write without duplicating its effect.

Updated

Step by step

  1. Capture the intent

    Keep the operation’s original request ID, account, expected revision and exact input before dispatch. Some compatibility operations do not offer durable receipts; read their individual contracts.

  2. Check after a lost reply

    Use the matching operation or original-status read. A timeout is uncertainty, not evidence that the write failed.

  3. Retry only the same intent

    When retry is supported, reuse the exact original. A revision conflict requires a fresh read and review, not automatic replacement of the expected revision.

What happens next

Recorded outcomes describe historical writes. Current source reads separately describe what exists now; a replayed receipt does not prove that nobody changed the record afterwards.

Troubleshooting

Honor retry timing and explicit closure. Closing a retry does not roll back a recorded change or prove an expired request had no effect. A close that arrives while the same original is still being saved waits for that save, then reports it as recorded.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READget_job_hunt_operation

Read a saved JobHunt operation after a retry or lost response. Use the original operation ID or request ID and operation name; optionally bind the expected payload hash. Full profile-photo receipts expose original non-secret photo artifact IDs in data.related_ids. Payload-hash-bound application-document customization checks also expose the exact created role-document ID. Payload-hash-bound submission-report checks expose the exact reported submission ID. Other receipt namespaces do not expose related IDs. Never repeat an uncertain create with a new key.

GET /api/v1/journey/get_job_hunt_operation

DECLARED PERMISSIONS

  • read:profile
  • read:applications
  • read:documents
  • read:campaigns
  • read:tasks
  • read:contacts
  • read:interviews
  • read:companies
  • read:calendar
View input, output and access requirements →
READget_document_version_original_v1

Read the recorded outcome of one exact checkpoint or restore original. Captured account, canonical original fields and their payload hash must match the existing receipt. Reports immutable checkpoint/restore IDs and original revision even after later source edits or source removal. Does not read document bodies, retry a write or claim current content equals the restored snapshot.

GET /api/v1/journey/get_document_version_original_v1

DECLARED PERMISSIONS

  • read:documents
View input, output and access requirements →
WRITErestore_document_snapshot_v1

Restore the exact owned native snapshot without a bounded career-fact response projection. Returns a content-minimal recorded revision; read saved content with get_document_version_file. Uses the same restore_document_revision original, receipt namespace, current-revision check and explicit retry/closure. Preserves unknown provenance and current linked-profile choices; never restores or infers a profile link.

POST /api/v1/journey/restore_document_snapshot_v1

DECLARED PERMISSIONS

  • write:documents
View input, output and access requirements →