Appearance

n8n: Work ​

7 active flows.

Summary ​

FlowTriggerCallsProcsTables
Work queue - Claimwebhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/claim010
Work queue - Dead letter digestschedule: every 1 hours013
Work queue - Depthwebhook GET /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/depth010
Work queue - Portal send reservewebhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/portal-send/reserve000
Work queue - Prime budgetschedule: every 5 minutes011
Work queue - Sealwebhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/seal010
Work queue - Settlewebhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/settle012

Flows ​

Work queue - Claim ​

Work queue - Claim One of the four gateway routes. The Ethos database firewall admits the n8n host and nothing in the Container Apps Environment, so a worker reaches the queue procedures through here and nowhere else. Body: { "queueName": "...", "consumerId":

  • Triggers: webhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/claim
  • Nodes: 4 · Integrations: SQL
  • Stored procedures: spEthWorkQueueClaim_Preview

Work queue - Dead letter digest ​

Work queue - Dead letter digest The one alert in the system. A dead message is the only thing that waits for a human, and a stuck seal is the only other. A portal failure is not an alert: it is a failed attempt on the backoff curve, visible as ScheduledCount.

  • Triggers: schedule: every 1 hours
  • Nodes: 8 · Integrations: SQL, Outlook
  • Stored procedures: spEthWorkQueueDepth_Preview
  • Tables/views read or written: ethWorkQueueMessage_Preview, ethWorkQueue_Preview, ethWorkQueueAttempt_Preview

Work queue - Depth ​

Work queue - Depth What KEDA reads. Each worker's Container Apps Job carries a metrics-api scale rule pointing at GET .../work-queue/depth?queueName=<its queue with valueLocation: ClaimableCount and the gateway key in x-api-key. One claimable message starts on

  • Triggers: webhook GET /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/depth
  • Nodes: 5 · Integrations: SQL
  • Stored procedures: spEthWorkQueueDepth_Preview

Work queue - Portal send reserve ​

Work queue - Portal send reserve The hourly verification-code budget, counted where the work queue already lives. A supplier portal sends a code when credentials are submitted and allows only three an hour, and the staff who share those accounts draw on the sa

  • Triggers: webhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/portal-send/reserve
  • Nodes: 4 · Integrations: SQL

Work queue - Prime budget ​

Work queue - Prime budget Prime rate-limits the whole company by day: two API accounts, 5000 calls each. A lane that creates Prime jobs can spend the budget that ungated critical work (Make Safe job sync) needs later the same day. The old Depth API checked thi

  • Triggers: schedule: every 5 minutes
  • Nodes: 4 · Integrations: SQL
  • Stored procedures: spN8nGetPrimeRateLimitPercent
  • Tables/views read or written: ethWorkQueue_Preview

Work queue - Seal ​

Work queue - Seal The point of no return on an at-most-once queue. A worker calls this immediately before its irreversible write: Optimo before Share Routes opens, the Repairline submit worker before the Prime job is created. A sealed message can be claimed by

  • Triggers: webhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/seal
  • Nodes: 4 · Integrations: SQL
  • Stored procedures: spEthWorkQueueSeal_Preview

Work queue - Settle ​

Work queue - Settle Closes an attempt under its claim token. The worker calls this once per message from its success path and from every failure after the claim; the queue decides the message's next status from the outcome. Body: { "messageId", "claimToken", "

  • Triggers: webhook POST /92b73ebd-ffbf-4720-a3ee-ed408fb854e6/work-queue/settle
  • Nodes: 8 · Integrations: SQL
  • Stored procedures: spEthWorkQueueSettle_Preview
  • Tables/views read or written: ethWorkQueue_Preview, ethWorkQueueMessage_Preview