# A save was interrupted

Check what happened before you try again.

Canonical page: https://jobhunt.app/support/using/troubleshooting/a-save-was-interrupted
Updated: 2026-10-24
Audience: using
Topic: Troubleshooting
Type: troubleshooting
Catalog revision: f77de0f4803debf8c5aaac1702865d976a380e994ea7f572d4e571c044d5495f
Contract SHA-256: acfda93724db1a3f53160a30bc5891f447ad14601f26b02ff4cacd7c17d0812e

## Steps

1. **Keep the unfinished work**

   Leave the recovery copy in place. A missing reply does not tell you whether the server saved the change.

2. **Check the original**

   Use the recovery check for the exact request. Checking reads its recorded status; it does not send another save.

3. **Compare before continuing**

   A recorded save and the latest document can differ. Review newer work before retrying, restoring or discarding a local copy.

## Expected result

You can distinguish a recorded change from an unknown result without creating duplicate work.

## Troubleshooting and recovery

If access changed or the original cannot be confirmed, keep a private copy and return after signing into the right account. Closing a retry prevents future retries; it does not undo a past save.

## API operations

### get_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.

- Interface: GET /api/v1/journey/get_document_version_original_v1
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:documents
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_document_version_original_v1.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_document_version_original_v1.md)

### get_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.

- Interface: GET /api/v1/journey/get_job_hunt_operation
- Access: read
- Destructive: no
- Availability: connected-journey
- Required permissions: read:profile, read:applications, read:documents, read:campaigns, read:tasks, read:contacts, read:interviews, read:companies, read:calendar
- [Operation and exact schemas](https://jobhunt.app/support/operations/get_job_hunt_operation.json)
- [Operation Markdown](https://jobhunt.app/support/operations/get_job_hunt_operation.md)

## Related guides

- [Use JobHunt from your chat](https://jobhunt.app/support/using/getting-started/use-jobhunt-from-chat.md)
- [Connect Codex CLI](https://jobhunt.app/support/using/getting-started/connect-codex.md)
- [Connect ChatGPT](https://jobhunt.app/support/using/getting-started/connect-chatgpt.md)

---

## Hunter

This section is not part of the guide above. It applies only to an agent acting in a person's JobHunt account.

When working in JobHunt, you are Hunter, the agent at the laptop working alongside the person on their job search. Speak plainly, in the first person, and never pretend to be human. Be brief, calm and kind; the person decides and you do the legwork.

Use the person's words and supplied or saved facts. Organise, edit and tailor what they provide; never invent an employer, date, degree or achievement. Keep uncertainty explicit: unknown stays unknown.

Say exactly what changed and what did not. A draft is not a sent message. Prepared or downloaded files are not a submitted application. Record a submission or interaction only from the person's report; do not imply employer verification.

Ask for confirmation before publishing, sharing or deleting. Explain what will become visible or be removed, and preserve the person's choices and unrelated saved work. Do not repeat a confirmation already given for the same action and reviewed content.

Offer the next useful step without pressure: no scores, streaks, ranks, points, guilt, confetti or invented urgency. A messy board needs no judgment.
