ReadonlyserviceStable, human-readable name for the service. Must be set explicitly on each subclass
because this.constructor.name gets mangled by minification in production builds,
which breaks tracing/observability span names.
ProtectedloggerProtectedrunProtectedspanOptional hook for subclasses to attach extra non-PII span attributes derived from params.
The returned attributes appear on the service.${serviceName} span (and, for jobs,
on job.enqueue.* and job.run.* spans too).
Safe ID-like keys on params (e.g. patientId, templateIds, limit, cursor) are
already auto-extracted via toSpanAttributes("service.input", params) — you don't need
to enumerate them here. Use this hook for derived/computed attributes (counts, flags,
computed names) or for fields you've explicitly verified safe but that aren't in the
global allowlist. Hook output overrides auto-extracted attributes on key collision.
Safe by default: returns {} when not overridden. Only declare keys you've confirmed
are non-PII. Never include emails, names, dob, free-text, etc.
ProtectedspanOptional hook for subclasses to attach extra non-PII span attributes derived from the
successful service result. Only called when run resolves successfully; on error, the
span is marked via markSpanError instead.
Safe by default: returns {} when not overridden. Only declare keys you've confirmed
are non-PII (e.g. counts, status flags, computed summaries). Never include emails,
names, dob, free-text, etc.
Re-submits a settled Extend extraction as a fresh workflow run. The original source PDF's bucket URL rides in the webhook metadata we attached at submit time (
sourceFileUrl, echoed back inraw_payload); we re-sign it and submit to the same workflow with the same correlation metadata, so the new run flows through the normal webhook/ingest pipeline and is tracked as its ownextend_runsrow (linked to the same originating RPA run, if any).Throws
ExtendRunSourceFileMissingErrorwhen the run predates source-URL tracking (no webhook payload yet, or nosourceFileUrlin its metadata) — those runs can only be redone by re-running the RPA sync itself.