Scheduled API Key Expiry Notification Not sent
search cancel

Scheduled API Key Expiry Notification Not sent

book

Article ID: 404594

calendar_today

Updated On:

Products

CA API Developer Portal

Issue/Introduction

In some cases, the Expiry Report notification email is not received when it is Scheduled from Report Cadence in Expiry Reporting tab.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-developer-portal/5-3/set-up-and-maintenance/application-key-settings.html

Error from portal-data log for failed notification.

[system-portal.log] [2025-07-15 00:35:00,025] [INFO ] [c.l.p.s.r.s.AuthenticationFactory] [TaskScheduler-5] [6875a234c9f448f3e8e2377d8bb42e2c|e8e2377d8bb42e2c] [|||] Creating authentication for user Scheduler Service 
[portal.log] [2025-07-15 00:35:00,083] [ERROR] [o.s.s.s.TaskUtils$LoggingErrorHandler] [TaskScheduler-5] [|] [|||] Unexpected error occurred in scheduled task 
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.layer7.portal.organization.dataaccess.OrganizationEntity.tags, could not initialize proxy - no Session

Environment

API Portal 5.2.3

Resolution

There is a bug in Portal 5.3.2 which is blocking the Expiry reporting notification scheduled job not triggering an email to the Org admin.

This has been fixed in API Developer Portal 5.3.3 .