Overview
Configure verification workers with endpoint, status, heartbeat, capacity, inflight state and credential handling so batch verification can be distributed.
Problem
Large verification workloads need durable coordination between Email Hub and multiple eligible processing workers.
Solution
Use the verification-worker registry, connector, capacity checks and repair worker to assign work while preserving job state and worker health.
How it works
verif-process selects ready capacity, sends bounded work to validated worker endpoints, updates verification state, and verify-heal repairs stale reservations or processing state. Administrators can manage status, heartbeat and credentials.
Who is this for
Expected outcomes
- Verification throughput can scale across configured workers
- Worker health, capacity and stale state remain visible and repairable
Key metrics
Security impact
- Verification worker endpoints, credentials/references, heartbeat, capacity, inflight state, assignments and job results · PII: yes where email addresses, message content, attachments, recipients, or integration payloads contain personal data
Compliance
- Worker-management permissions
- AppSecretService-backed credential handling and external-network policy