Studies arrive but do not reach a destination
Symptom: the modality sent the study successfully, but it is missing from the PACS, or only partly there.
Find the study
Section titled “Find the study”Search History by accession number or patient ID, and open the study. It counts each destination’s instances as delivered, pending, failed or moved, and lists every instance with its state:
| What you see | Means | Next |
|---|---|---|
| Delivered (or Committed) | The destination accepted it. | The destination filed it elsewhere: check its own logs. |
| Pending: queued or retrying | Still waiting to be sent, or being retried. | See below. |
| Failed: dead-lettered | Refused for good, or out of attempts. | See Dead letters keep appearing. |
| Moved | Sent to another member of its group (failover). | Check that member. |
| Received as Held | The route waits for the whole study. | It goes once the study has been quiet for the route’s quiet time. |
| Received as Reconciling | Held for patient reconciliation. | History › Reconciliation. |
| Received as Filtered | The study did not meet the route’s study conditions. | Resend it by hand, or change the conditions. |
| No delivery to it | No route sent it there. | Route tester: which route took it? |
Still queued
Section titled “Still queued”Expand the node on the Nodes tab and look at the destination’s queue:
- Unreachable: the node cannot connect (network, port, the destination is down) or the destination rejects the association (it does not know the router’s AE title or the node’s address). The last error says which.
- Paused or rate-limited: its schedule is holding it.
- Held: it cannot send at all yet. The reason is shown, such as a de-identification key or patient ID map not yet received from the central service.
- A long queue that moves: the destination is slow; more associations per node or a larger asynchronous window may help, if the destination supports them.
Not routed there at all
Section titled “Not routed there at all”If the study has no delivery to that destination, the first matching route did not include it. Remember that routes do not combine: the first matching route decides. Use the Route tester with the sender and the study’s header values.