An Import or Queue Is Stuck

The Import Rejected Everything

A run that rejects every row is almost never a data problem. It means ClaimPod could not read the file in the shape the mapping template expects, usually because the file changed.

Fix: compare the file against the mapping template before working rows individually. Correct the template, then re-run the import.

Complete Is Not There

You are looking at a Queued item. Selecting an item opens it for viewing only, so browsing a colleague’s queue never takes their work.

Fix: make your first edit. The item becomes In Progress, and Complete and Skip appear.

Complete Refuses

Completion validates before it closes anything, so an item cannot be closed over an unresolved problem. ClaimPod names what is still blocking it and stays where it is.

Fix: resolve what it names, then complete again.

The Record Is Gone

This claim no longer exists.

The underlying record was deleted or superseded while the item sat in the queue. A re-run of an import supersedes its earlier review items the same way.

Fix: skip the item to keep the queue moving.

My Edits Disappeared

They should not have. Workspace edits save as a draft continuously, and a recovered draft announces itself when you return.

Fix: if a draft genuinely did not restore, report it through Feedback in the header, with the queue and item number.

Related: Work a Queue Item · Review an Import Row