We’re experiencing significant delays in email notifications when our CAPA module triggers external workflow integrations. The CAPA record creates successfully and the integration fires, but stakeholders report receiving notification emails 45-90 minutes after the actual event.
I’ve checked the notification job queue and see entries piling up during peak hours. The job scheduler seems to be processing them sequentially rather than in parallel. Our message broker monitoring shows the messages are queued properly but processing is slow.
Has anyone dealt with notification job queue bottlenecks in CAPA integrations? We’re on MC 2023.1 and this started after we added three new external workflow connections. The delay is impacting our response times for critical CAPAs.
I’ve seen similar behavior with notification delays. First thing to check is your notification job scheduler configuration - specifically the thread pool size and priority settings. If you’re processing notifications sequentially with a single thread, that’s your bottleneck. Also verify your message broker isn’t hitting connection limits during peak loads.
One thing nobody mentioned yet - check your message broker monitoring for acknowledgment timeouts. If your external workflow integrations are slow to acknowledge receipt, the broker might be holding messages in an unacknowledged state, which blocks subsequent notifications. We had a third-party system taking 30+ seconds to ACK messages and it created a cascade delay across all notifications.
Thanks for the suggestions. I checked the thread pool and we’re only running 2 threads for notification processing. That seems low for our volume. Where in the admin console can I increase this? Also, how do I verify the priority settings for CAPA notifications specifically?