NotificationFailure event

Highlight

Event	Description	How to recover	Flow Related
NotificationFailure	• Emitted when handling/sending a notification related to bulk processing fails	• Check notifier endpoint e.g. kafka is available • Any behaviour depending on the notification will need to be executed manually. E.g. if your application is subscribing to a BulkClosedNotification to send an email, the email will need to be sent manually	no

Event

Description

How to recover

Flow Related

NotificationFailure

• Emitted when handling/sending a notification related to bulk processing fails

• Check notifier endpoint e.g. kafka is available
• Any behaviour depending on the notification will need to be executed manually. E.g. if your application is subscribing to a BulkClosedNotification to send an email, the email will need to be sent manually

Operating Questions

Question	Answer	Comments
Could happen in production?	Yes
Is it fatal?	No	Not fatal in relation to processing of bulks, but will mean actions driven off bulker notifications will not be triggered.

Question

Answer

Comments

Could happen in production?

Yes

Is it fatal?

Not fatal in relation to processing of bulks, but will mean actions driven off bulker notifications will not be triggered.

Logs

Log level Log message Also logs underlying exception?

Log level	Log message	Also logs underlying exception?
ERROR	`Error encountered sending {Notification class name}`	Yes

ERROR

Error encountered sending {Notification class name}

Yes

Resolution Notes

This System Event occurs from an issue sending a notification via the BulkNotificationPort.

#	Action	Comments
1	Check system logs and the system event for underlying exception.	Look for the ERROR log mentioned in the 'Logs' section. The System Event also logs the error in the errorMessage field.
2	Investigate and resolve underlying issue	This depends on the client implementation of the BulkNotificationPort interface. IPF provides a pre-packed implementation of this interface in the ipf-bulker-notifications-connector-kafka maven artefact that publishes notifications to kafka. If the client is using this, check Kafka health (specifically the notifier endpoint and topic (default topic is BULK_NOTIFICATION))
3	Manually send the failed Notification OR Manually trigger the dependent behaviour	If the underlying issue has been resolved, you can manually fire-off the failed notification if you have access to the fields required to re-construct the notification object. Alternatively, any behaviour or process that is driven from the specific notification that failed can be manually triggered.

Action

Comments

Check system logs and the system event for underlying exception.

Look for the ERROR log mentioned in the 'Logs' section.

The System Event also logs the error in the errorMessage field.

Investigate and resolve underlying issue

This depends on the client implementation of the BulkNotificationPort interface.

IPF provides a pre-packed implementation of this interface in the ipf-bulker-notifications-connector-kafka maven artefact that publishes notifications to kafka. If the client is using this, check Kafka health (specifically the notifier endpoint and topic (default topic is BULK_NOTIFICATION))

Manually send the failed Notification

Manually trigger the dependent behaviour

If the underlying issue has been resolved, you can manually fire-off the failed notification if you have access to the fields required to re-construct the notification object.

Alternatively, any behaviour or process that is driven from the specific notification that failed can be manually triggered.