-
Notifications
You must be signed in to change notification settings - Fork 82
Scheduler: Process batches for individual hooks #1521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Conversation
First pass. It'll need a bit more testing. |
I will run some tests on my live system tomorrow morning. |
I have the same issue when "flooding" the db with comments. It seems that only 2 of 5 to 7 comments will be queued properly. If I trigger the Might there be a flood control mechanism that still interferes somehow? |
Yeah, I wouldn't expect this PR to help with that directly. But it should help with more fine-grain control over identifying specific jobs |
Except from the flooding issue, everything seems to work as before... Have to check the retries though... I have no broken followers on my second blog 🫣 |
I have some really weird experiences on my live system. Have to observe that a bit. |
4c06690
to
0b36dc1
Compare
0b36dc1
to
8b236f7
Compare
Removed my changes... will think about logging in general... |
Proposed changes:
next_scheduled_hook()
method, as it is no longer used.Other information:
Testing instructions:
npm run env -- run cli wp cron event run --all
ACTIVITYPUB_OUTBOX_PROCESSING_BATCH_SIZE = 1
to trigger batching)Changelog entry
Changelog Entry Details
Significance
Type
Message
Batch processing jobs can now be scheduled with individual hooks.