Claims sent to OnBase for Retention Processing. OnBase Document ID: id
stdout
Batch archived
THRDPARTY_RETENTION records marked as processed. ID List:
stdout
Batch marked
No claims eligible for retention policy deletion.
stdout
Nothing to do (exit 0)
Error: message
stderr
Unhandled exception caught by Execute and reported before exit (exit 5); argument-validation failures instead exit 1 with no Error: line, and application-resolution/startup failures also exit 5 but are reported directly by the runner without an Error: line
For a startup/resolution failure (no Error: line, no start header — see Run lifecycle), inspect the runner's reported exception on stderr directly; for a failure during processing, read the Error: line. Use the scenarios below either way.
Check the Imaging API; the client already retried transient statuses
OnBase FaultException, CommunicationException, or timeout
OnBase endpoint unreachable or rejecting the call*
Check the OnBase service and endpoint address
Run failed after the OnBase log line but before the marked line
Mark-processed call failed
Rerun; the batch may be resubmitted to OnBase*
Exit 0 with no claims on a day that should have claims
Empty or unparseable API response is treated as none*
Verify the Imaging API response for the date
Rerunning is the only recovery path; completed batches are not rolled back. See BR-OB3P-007. Whether OnBase deletes documents after a submission is unknown.**
Note: Statements marked with * were inferred from code structure, naming
conventions, or contextual evidence where direct confirmation was not available
in source artifacts. Statements marked with ** could not be confirmed; treat
as unknown until verified.