PACI Share-Link Resolution (WhatsApp → Hermes → Kuwait Finder)

PACI Share-Link Resolution (WhatsApp → Hermes → Kuwait Finder) A workflow diagram generated by Archify. 01 / WhatsApp Customer 02 / Hermes Server (VPS) 03 / Kuwait Proxy (paci-kw) EX / PACI (Government) Intake Resolve Respond Retry and fallback Kuwaiti egress IP Customer Link · gis.paci.gov.kw/?id= · WhatsApp Customer › Intake Customer Link gis.paci.gov.kw/?id= WhatsApp Reply · no raw timeout · WhatsApp Customer › Respond WhatsApp Reply no raw timeout WhatsApp Bridge · pre-resolve link · Hermes Server (VPS) › Intake WhatsApp Bridge pre-resolve link Resolve Cache · 24h, hit skips PACI · Hermes Server (VPS) › Resolve Resolve Cache 24h, hit skips PACI kfFetch · 3 tries, 15s budget · Hermes Server (VPS) › Retry and fallback › Resolve · proxy, then direct kfFetch 3 tries, 15s budget proxy, then direct Degraded Intake · keep link, ask type + price · Hermes Server (VPS) › Retry and fallback › Resolve Degraded Intake keep link, ask type + price Hermes Agent · stage property intake · Hermes Server (VPS) › Respond Hermes Agent stage property intake /kfapp/ Route · nginx, secret path · Kuwait Proxy (paci-kw) › Kuwaiti egress IP › Resolve · Kuwait IP /kfapp/ Route nginx, secret path Kuwait IP Kuwait Finder API · kfappsrv.paci.gov.kw · PACI (Government) › Resolve · geo-blocked abroad Kuwait Finder API kfappsrv.paci.gov.kw geo-blocked abroad reply lookup miss ask only type + price all attempts fail try proxy first message address fields relay Legend User UI Agent logic Policy Tool action Context / trace Cloud service External system

Root cause

  • • PACI blocks datacenter IPs outside Kuwait
  • • kfappsrv was not relayed by the proxy

What changed

  • • New /kfapp/ route, tried first by kfFetch
  • • Retries, 24h cache, classified failures

Graceful degradation

  • • Keep the link, never mention a timeout
  • • Ask only for type and price
Suite ↗