Crawler Runs Delayed
Incident Lifecycle
Incident Timeline
Monitoring
We have resolved the delays causing Crawler runs to be stuck over the last ~34 hours.
As part of our resolution, we needed to cancel all active crawls. For customers with one-off or weekly crawl configurations, we have restarted all your crawls (and all but five weekly crawls are still in progress).
For customers with daily crawl configurations, you should feel free to manually restart your crawls, or expect that they will run again at their normally scheduled time in the next 24 hours.
As part of our resolution, we needed to cancel all active crawls. For customers with one-off or weekly crawl configurations, we have restarted all your crawls (and all but five weekly crawls are still in progress).
For customers with daily crawl configurations, you should feel free to manually restart your crawls, or expect that they will run again at their normally scheduled time in the next 24 hours.
May 13, 2026 at 6:10 PM UTC
Identified
Crawler runs are still delayed; we are continuing to work on figuring out the source of the delays.
May 13, 2026 at 6:37 AM UTC
Identified
We have identified an issue that has been causing delays in Crawler runs since 4:00 AM EST earlier today (May 12, 2026).
May 12, 2026 at 10:33 PM UTC
Was your business affected by this Yext outage?
Set up instant alerts for Yext, be the first to know about outages via email, Slack, Teams, or Discord.