01KJ3G96Y7VB8CT1ZARBR03MFX
Fiserv uCom call failures in payment-dgs for kfc_us
• Org: kfc_us • Env: production • Service: payment-dgs > [Troubleshooting Guide](https://yumbrands.atlassian.net/wiki/spaces/YCSD/pages/1518469121/Steps+for+Payment+500+Errors) Key Information: > Escalate Alert state incidents to Fiserv.If events are significantly greater than the historical trend, there may be an outage. Troubleshooting Steps: > 1. Identify what event(s) failed, how many and which Brand is impacted. > > 2. Reach out to the brand integration team to confirm if they are encountering/observing any issues. > > 3. Escalate the incident(s) to Fiserv. @slack-datadog-alerts @webhook-
Started: 2/22/2026, 8:22:32 PM
Duration: n/a
Source: imported
Root Cause and Resolution
Trigger:
Detection Gap:
Primary Cause:
Contributing Factors
Resolution:
Corrective Actions
Five Whys
Build This Skill
Training modules mapped to this incident.
Commerce Service Topology
Reading
Commerce Monitor Signals and Alert Quality
Reading
SRE New Hire Onboarding Baseline
Reading
Commerce User Journey and Failure Transitions
Reading
Commerce Incident Analytics and MTTx
Reading