Any support for APO subscribers?

As you stated, paying only for APO (USD 5.00/month) does not get you support via tickets or email. Purchasing a PRO Plan or above does.

Thanks, @generosus.

I don’t know if you are affiliated with Cloudflare, but here are my thoughts:

I can’t think of a service I’m paying for but can’t get any official support for. That includes services I’m paying a similar (and even smaller) amount for.

I understand Cloudflare doesn’t want to provide support for all of its free services for 5.00/month – but it can easily limit the support to APO-related issues.

After 3 weeks, I still can’t get a simple answer about what APO is supposed or isn’t supposed to do: does it automatically re-cache after purge (as official Cloudflare blog posts and the documentation suggest), or not (as practice suggests)?

Furthermore, all the WordPress plugins I’ve used and am using, and are still maintained, provide support here in the forums – and most of them are free.

Anyway, I canceled my APO subscription, mostly for not being able to get any sort of official support.

Have a great day.

Hey @asafm7,

Not affiliated with Cloudflare. We’ve been using APO for 3 years with no issues. Cloudflare has sufficient documentation to clarify most questions associated with APO.

To help you out, this should answer your questions: https://developers.cloudflare.com/automatic-platform-optimization/

Once you purge your cache, it takes 2-4 days for pages to be fully cached at the edge.

Online tools and header checks from remote locations confirm APO works as intended.

Best wishes!

Thanks @generosus.

To the best of my knowledge, WordPress nonces make most WordPress pages un-cacheable for more than 12 hours (unless nonces are extended or other solutions, such as ESI, are implemented).

For example: Nonces and Cache Lifespan – WP Rocket Knowledge Base (wp-rocket.me)

Taking this into account, and if indeed it takes 2-4 days for pages to be fully cached at the edge – APO doesn’t deliver on its promise and isn’t much better than the free Cache Everything feature.

I’m familiar with the documentation you referred to – it is part of the unclarity.

From the documentation:

Verify the APO integration and WordPress integration work

Open your WordPress site and publish a change. When the integration is working, the page is cached with cf-cache-status: HIT and cf-apo-via: tcache

From this, it can be understood that APO immediately re-caches after an update. Otherwise, it makes no sense to instruct users to search for cf-cache-status: HIT on the first visit after an update – they should actually search for cf-cache-status: MISS.

As you described though, it doesn’t seem to be the case.