OnBaseKeywordSync is invoked with no arguments, runs a single Execute-stage batch operation, and produces a binary success/failure exit code (0 or 5). This page collects the operational facts an on-call engineer needs to triage a failed or unexpected run.
UC4 (per README.md: "run from UC4", "Called from many different UC workflows"); no job definition file exists in this repository
Upstream dependencies
Not determined from source
Downstream dependents
Not determined from source
Pipelines/build.yml and Pipelines/release.yml both declare trigger: none and contain only build/deploy stages; no scheduler definition file exists in this repository.
Log destinations are configured through machine-level environment variablesfile0–file4 on the host that runs the executable. Each variable's value is a log file path.† These are simply named log-file destinations — an application convention, not a control/detail/error stream contract.
Environment variable
Content
Retention
file0–file4
Not used — the application registers no log file explicitly and assigns no specific role to any id. Whatever is registered receives every Write/WriteError message†
Not determined from source**
A separate debug-only tee writes to C:\temp\OnBaseKeywordSync_Debug.log (from appSettings key debugLogFile) only when a debugger is attached, and the file is truncated at every process start regardless of debugger state — see Tech debt.
Escalate with the formatted exception from standard error — the only failure code this application produces. Typical causes: Imaging API HTTP failure, OnBase WCF fault/timeout, missing customquerymappings entry for a doc type group, or a configuration key that fails to convert
6
No data found
Not used — an empty unprocessed set logs a zero-record summary and exits 0
Exception during ImagingApiClient calls, "Error syncing OnBase claim data. Error: {ex.Message}" on stderr, exit code 5
No records processed for this run
Verify imagingapiurl for the configured track and Imaging API availability, then re-run
OnBase SOAP endpoint unreachable, faulted, or times out
WCF exception, exit code 5
Batch aborts mid-run; records already marked processed are not rolled back*
Verify OnBaseKeywordUpdateServiceUrl and OnBase service availability, then re-run; manually reconcile any records marked processed without a confirmed OnBase update
Doc type group missing from customquerymappings
KeyNotFoundException, exit code 5
Batch aborts at the first unmapped record
Add the missing DTG\|query pair to OnBaseKeywordSync.customquerymappings for the affected track, then re-run
onbaseasync missing or non-boolean
Conversion exception, exit code 5
Application aborts before any record is processed
Verify the OnBaseKeywordSync.onbaseasync value is declared and boolean for the configured track
One record's update fails mid-batch
Exception propagates, exit code 5
Remaining records in the batch are never evaluated; there is no per-record error isolation*
Investigate the failing record, correct the underlying data or configuration, then re-run — already-processed records are not resent
enttest8 track malformed settings
Three settings (getdocumentcount, onbaseclientsleepmilliseconds, customquerymappings) have no declared value on enttest8 due to a false:/value: YAML defect
Behavior on that track depends on undetermined fallback behavior**
Fix environmentsettings/settings.yml to use value: instead of false: for the three enttest8 entries
Note: Statements marked with † are derived from dependency library documentation via the Legends CLI. Statements marked with * were inferred from code structure or contextual evidence. Statements marked with ** could not be confirmed; treat as unknown until verified.