Search
One result set across ServiceNow, Teams, the knowledge base and uploaded documents.
daraja timeoutService · Daraja APILast 90 daysSev 1–2Sort · Best match
Source
Record type
Results are filtered to what you can see, at query time.
1,284 results
Ranked by match, then recency. Evidence shown is the passage that matched.
Incident · Sev 2Resolved94% match
INC0048231: Daraja API returning 504 on the token endpoint
…intermittent 504 timeout responses from /oauth/v1/generate beginning 09:12. Connection pool exhaustion on gateway node 3 confirmed by…
INC0048231ServiceNow · 13:05 today
Conversation · TeamsDPIA-gated88% match
#noc-payments · 41 messages, 14 Aug
Wanjiru Mwangi: “same daraja timeout pattern as June. it clears if you drain node 3 first, then restart the token service. don’t restart both at once”
Problem · Open81% match
PRB0003318: Recurring gateway connection pool exhaustion
Six linked incidents across Daraja API and M-PESA API Gateway since June. Root cause unconfirmed; workaround documented in KB0010992.
PRB0003318ServiceNow · 13:05 today
Knowledge base76% match
KB0010992: runbook for draining and restarting the Daraja token service
Step 1: confirm the node from the gateway dashboard. Step 2: drain connections before restart. Step 3: verify token issuance before returning the node to the pool…
KB0010992ServiceNow · 2 Jul
Document · PDFConfidential68% match
IA-2025-114: Token expiry is not monitored end to end
Finding: no alerting exists on token issuance failure rates. Owner: Grace Wanjiku. Status: open, due 30 Sep 2026. Applies to Daraja API and M-PESA API Gateway.
AUDIT · IA-2025-114Uploaded · 12 Aug
3 further results are hidden. They sit in channels and documents you don't have access to.Request access