If there are no items to process on cron, should not log

Created on 26 August 2024, 4 months ago

Problem/Motivation

When a Batch operation is run by cron and there are no items to process, the system should not log it because this can get pretty noisy for no good reason. Otherwise the logs will get flooded by no-ops.

Other more intentional runs by drush or UI or other calls should log, but not cron.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request

Status

Fixed

Version

1.0

Component

Code

Created by

🇺🇸United States swirt Florida

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @swirt

Comment 4 months ago →

System Message

swirt → committed 5971c59d on 1.0.x

Issue #3470335 by swirt: If there are no items to process on cron,...

Status changed to Fixed 4 months ago6:44pm 26 August 2024
Comment 4 months ago →
🇺🇸United States swirt Florida
Status changed to Fixed 4 months ago6:55pm 26 August 2024
Comment 4 months ago →
🇺🇸United States swirt Florida
Went out with release 1.0.3 →

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024