[wp-trac] [WordPress Trac] #64373: To developers bug report / suggestions:
WordPress Trac
noreply at wordpress.org
Tue Dec 9 20:00:19 UTC 2025
#64373: To developers bug report / suggestions:
-------------------------------+------------------------------
Reporter: hellobonjour2025 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Cron API | Version: 6.9
Severity: normal | Resolution:
Keywords: reporter-feedback | Focuses:
-------------------------------+------------------------------
Changes (by jorbin):
* keywords: => reporter-feedback
* severity: critical => normal
Comment:
hi @hellobonjour2025, welcome to WordPress Trac.
You seem to be mentioning a handful of things, so I am going to try to
address all of them but please note that Trac is used for tracking
specific bugs and/or enhacements, not for general feedback.
> Working with developers of Cloudflare and making it compatible.
If the team from Cloudlare, a commercial service, wishes to donate some
time to WordPress, they are welcome to. If you are a customer I would
encourage you to work with your account manager to make sure they know you
want them to focus on ensuring they work well with WordPress.
> Perhaps combining API calls as one to one service only – would be a
solution for millions.
There are three types of calls:
1. Calls from your browser to your WordPress install. In general, attempts
are made to have these are included in the HTML response where possible or
the using the [https://make.wordpress.org/core/2020/11/20/rest-api-batch-
framework-in-wordpress-5-6/ batch endpoint]. Heartbeat API is configurable
by adjusting the `heartbeat_settings` filter.
2. Calls from your WordPress install to WordPress.org checking for
updates. Each of these is a separate endpoint and done as a separate call
in order to allow them to be more customizable. By default, these calls
are twice a day each for plugins, themes, and core.
3. Calls from your WordPress install back to itself. These are done to
ensure that cron is triggered. You can
[https://developer.wordpress.org/plugins/cron/hooking-wp-cron-into-the-
system-task-scheduler/ configure your install to use system cron] instead
if you are worried about these calls. These are also done as a part of
health check but will only trigger by visiting the health check page.
If you are interested in working on changing one of these, I would
encourage you to open a ticket for that one task. If I missed something
you are looking to discuss, please comment here otherwise I will plan to
close this out.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64373#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list