CAUAJM_W_00097 Ignoring email address <[email protected]> on behalf of job <job_name> with run number <123.1> due to error: <452 Too many recipients received this hour>
Article ID: 438028
Updated On:
Products
Issue/Introduction
AutoSys job notifications fail to reach specific email addresses or distribution lists (DLs). The following warning messages are observed in the event_demon log:
[04/02/2026 13:52:53] CAUAJM_W_00097 Ignoring email address <[email protected]> on behalf of job <example-job> with run number <123.1> due to error: <452 Too many recipients received this hour>- The issue persists even after the mail server administrator increases the throttle or rate limits.
- Notifications to other email addresses or DLs continue to work normally.
- Testing the problematic DL outside of AutoSys (e.g., via manual SMTP test) works successfully.
Cause
The issue is caused by the AutoSys scheduler's in-memory "bad recipient" cache.
When the SMTP server returns a transient or permanent error (any response code other than 250 OK), the event_demon process stores the email address and the specific error message (e.g., 452 Too many recipients) in an internal map.
Per current design, once an address is cached as "bad," the scheduler skips all future notification attempts to that address for the life of the process. It does not attempt a new SMTP connection for cached addresses, meaning it will never detect when the underlying mail server issue (like throttling) has been resolved.
Resolution
To clear the internal cache and force the scheduler to attempt a fresh SMTP connection, the scheduler must be refreshed or restarted.
Step 1: Refresh the Scheduler (Recommended)
Refreshing the scheduler forces it to reload configuration and flush the wrong_emails cache without impacting active job processing.
On Windows platform, pause and resume the Scheduler Service. On Linux, a kill -HUP <scheduler_pid>
Step 2: Restart the Scheduler (Alternative)
If a refresh does not resolve the issue, a full restart of the scheduler service will clear all in-memory caches.
On Windows platform, restart the Scheduler Service. On Linux, unisrvcntr restart waae_sched.<instance>
Step 3: Verification
Trigger a job that sends a notification to the previously failing address. Monitor the event_demon log for the success message:
CAUAJM_I_20209 Email notification sent successfully for job...Additional Information
The current behavior requires a manual refresh to clear the cache. A configurable expiration or automatic flushing of the email cache is being considered for a future release.
Broadcom RFE process:
Feedback
