ECA throwing error on aging content

[omahane]

Describe the defect

The recent logs contained 2 errors from 26 Aug 2024:

Failed execution of Queue Notification (create_advancedqueue_job) from ECA Aging Content: 
Expired FWB (aging_content_expired_fwb) for event Drupal\eca_content\Event\ContentEntityCustomEvent: 
Invalid values given. Values must be of scalar types, entities, stringable or typed data objects

To Reproduce

Steps to reproduce the behavior:

1. Go to the CMS on Tugboat
2. Run cron
3. Check the Recent logs
4. Filter for eca

• Confirm that the logs contain errors for each Aging Content item queued.

AC / Expected behavior

ECA should not be throwing an error on aging content.

Screenshots

I first encountered this while running cron on the PR instance for the 10.3.2 upgrade.

Additional context

We had been having issues with ECA not sending the Aging Content notifications, which @dsasser addressed in #18721.

In fact, PROD shows these as having been successfully sent: https://prod.cms.va.gov/admin/config/system/queues/jobs/aging_content

It's possible that they were successfully sent and threw an error. I have reached out to @RLHecht on Slack to confirm.

[dsasser]

Also seeing this error for the aging_content_expired_news_promo queue execution:

Failed execution of Queue Notification (create_advancedqueue_job) from ECA Aging Content: Expired V2 News Spotlight (aging_content_expired_news_promo) for event eca.content_entity.custom: Invalid values given. Values must be of scalar types, entities, stringable or typed data objects..

[dsasser]

Verified on prod: there are no ECA errors in the log.