# Troubleshooting

Diagnose missing records, incomplete preparation and verification failures.

## No transaction appears

1. Check institution, environment, application and time filters.
2. Confirm that the SDK can read its configuration.
3. Match the actual HTTP method/path or operation name to the active entry definition.
4. Confirm the service’s application connection.
5. Inspect TLS trust and delivery diagnostics.

After changing configuration, send a new request. Existing executions are not recreated automatically.

## Preparation is still in progress

Expand the row’s progress details. The root operation may still be running, a step may be incomplete or delivery may be pending. Progress reflects observed information; an unknown total workload cannot produce a reliable completion percentage. Do not emit a false completion event to force readiness.

## ReadTimeout and RemoteProtocolError

ReadTimeout relates to a response not being read within the expected interval. RemoteProtocolError relates to the remote protocol exchange. Neither alone establishes why a model failed. Inspect the actual target, time and error details in the same context. Observation does not repair a dependency failure.

## Verification does not complete

Check that files belong to the intended transaction, downloads are complete and keys are trusted. Do not generate a replacement key or edit sealed content to conceal a mismatch. Escalate the error code and transaction identity to authorised operations staff.