CI Number
No response
Duplicates
Latest version
Describe the issue
When multiple <monitor> blocks are configured inside <contentMonitoring>, the background job only executes and outputs data for a single monitor. Even though there is matching content matching the query rules of other configured monitors, no email notifications are triggered for them, and the /api/2/sites/monitor endpoint only outputs the same single monitor instance.
Steps to reproduce
Steps:
- Content monitor is enabled by default in the
Project Configuration XML, <contentMonitoring> block (e.g., Content Expiring Tomorrow, Content Expiring In One Week, etc.).
- Update the cronjob for the monitor content to run each minute. In Global Config add
studio.monitoring.content.cron: '0 */1 * * * ?' # Every one minutes
3.Ensure there is at least one content item that meets the date criteria for each respective monitor's query.
- Wait for content monitoring job, then invoke the API endpoint:
{{baseUrl}}/api/2/sites/monitor
- Review the received email notifications and the API JSON response payload.
Relevant log output
Screenshots and/or videos
No response
CI Number
No response
Duplicates
Latest version
Describe the issue
When multiple
<monitor>blocks are configured inside<contentMonitoring>, the background job only executes and outputs data for a single monitor. Even though there is matching content matching the query rules of other configured monitors, no email notifications are triggered for them, and the/api/2/sites/monitorendpoint only outputs the same single monitor instance.Steps to reproduce
Steps:
Project ConfigurationXML,<contentMonitoring>block (e.g., Content Expiring Tomorrow, Content Expiring In One Week, etc.).studio.monitoring.content.cron: '0 */1 * * * ?' # Every one minutes3.Ensure there is at least one content item that meets the date criteria for each respective monitor's query.
{{baseUrl}}/api/2/sites/monitor
Relevant log output
Screenshots and/or videos
No response