Purge Cloudflare after Heroku Deploy

Wondering if anyone else is running a react app on Heroku and Cloudflare. Would appear to be pretty common. As part of the release script, i’m making an api request to purge the cache but my (some) users still get routed to the old build unless I manually log in and purge everything via the console. Has anyone run into this or has tips on how to resolve this?

Feels really strange since the API and the Dashboard should hit the same endpoint.

Definitely, although I did notice that the API doc shows a POST http request to /zones/:id/purge but the official package for Cloudflare still uses DELETE. On the Audit Log in my console, it shows the same thing though.

Maybe try contacting support so that they can do some tests on their backend?

To contact Cloudflare Customer Support, login & go to https://dash.cloudflare.com/?account=support and select get more help. Please give Support the complete details and link to your Community post. Here’s a bit of background on Cloudflare Support for reference:

Still no updates from the cloud flare support desk unfortunately.

What’s the Ticket #?

1 Like