# \#wp\_gf\_telemetry\_processor\_cron

**URL:** https://community.gravityforms.com/tag/wp-gf-telemetry-processor-cron/2891.md

[Latest](https://community.gravityforms.com/latest.md) · [Categories](https://community.gravityforms.com/categories.md) · [Tags](https://community.gravityforms.com/tags.md)

---

## [GF Telemetry cron brought our website to its knees](https://community.gravityforms.com/t/gf-telemetry-cron-brought-our-website-to-its-knees/17633)

<div class="topic-metadata">

**Author:** [@user5b27be381e4f09.5](https://community.gravityforms.com/u/user5b27be381e4f09.5)\
**Replies:** 0\
**Last updated:** [June 7, 2024, 2:41pm UTC](https://community.gravityforms.com/t/gf-telemetry-cron-brought-our-website-to-its-knees/17633 "2024-06-07T14:41:07Z")

</div>

Hi, Yesterday we had a bad moment when our primary website started throwing 503 errors. While there were multiple factors at play, one item that was highlighted as a major slow point was wp\_gf\_telemetry\_processor\_cron.…