Most GearDock exceptions are deliberate stops: the system is explaining which prerequisite is missing rather than silently guessing or bypassing a decision. Start with the affected record and work backward through the visible evidence.
Import and Matching
| Symptom | What to check |
|---|---|
| A row is invalid | Review the mapped column, source value, required identifier, and row-level validation message before retrying. |
| A match is ambiguous | Compare manufacturer, model, SKU and UDI-family identifiers. Confirm the product manually or leave the row unresolved. |
| A source document is not available | Confirm the file belongs to this organization, finished processing, and is attached to the intended product. |
Draft and Claim Firewall
- An unsupported field stays empty until a source supports it.
- A conflict requires a person to inspect the competing passages and record the resolution.
- A blocked claim must be revised, removed, or supported; changing its wording does not create evidence.
- If extraction appears wrong, correct the source linkage or extracted fact through the governed workflow rather than editing audit history.
Approval, Release, and Export
Approval applies to a specific content version. If that version changes, review the new version. Release is a separate state and may be reversed. Export re-checks current governance and release state when it runs, so a previously queued job may stop after a decision changes.
Integration Execution
- Configuration error: verify the authorized account, scope, mapping, and destination boundary.
- Rate limited: allow the bounded retry policy to follow provider guidance instead of repeatedly starting new jobs.
- Retry exhausted: inspect the dead-letter reason and destination response before requesting a controlled retry.
- Interrupted run: check its last checkpoint and current lease state; do not create a duplicate run to work around a delay.
- Draft not visible downstream: confirm the profile's non-live publication state and the connected account or folder.
Safe Support Information
Share the organization-safe job or record reference, time, visible error code, provider profile, and steps already tried. Do not send passwords, API keys, connection strings, session cookies, patient information, or private source documents through a public form.