Errors in Management API

Incident Report for Yext

Postmortem

Summary

Starting around 5:30PM ET on April 24th, 2025, approximately 4% of calls to Yext’s Management API failed to complete. This, in turn, led to downstream errors in certain reseller flows and custom dashboards, although no data was lost or corrupted. By 5:30AM ET on April 25th, the underlying issue was resolved, and service was restored to normal.

Root Cause

The issue was caused by a configuration change to Yext’s Users API, a subset of the management API,  as part of an ongoing migration to a new service framework. An incorrect deployment of this change led to issues during call routing from our API gateway, which led to errors for the subset of calls to this backend.

Remediation

The configuration change was rolled back, and the services redeployed, which restored them to full functionality. Going forward, we will add extra synthetic monitoring for the Management API to better catch this category of issue and add custom error routing for this type of gateway-backend communication.

Posted Apr 29, 2025 - 09:56 EDT

Resolved

This incident has been resolved.
Posted Apr 25, 2025 - 06:57 EDT

Monitoring

A fix has been implemented and we are monitoring the results
Posted Apr 25, 2025 - 05:35 EDT

Identified

The issue has been identified and a fix is being implemented.
Posted Apr 25, 2025 - 05:19 EDT

Investigating

We are currently investigating reports of errors for a subset of our Management API calls, which is also affecting some custom customer dashboards.
Posted Apr 25, 2025 - 05:16 EDT
This incident affected: Content (Management API).