FileDeletionFailed event

Highlight

Event	Description	How to recover	Flow Related
FileDeletionFailed	• Emitted when deletion of a file (e.g., produced or temporary bulk file) fails (permissions or file lock issues). - Delete is done when the RejectBulk command is sent	Release file locks and verify filesystem permissions. Manually delete the file or send a reject bulk command again	maybe

Event

Description

How to recover

Flow Related

FileDeletionFailed

• Emitted when deletion of a file (e.g., produced or temporary bulk file) fails (permissions or file lock issues). - Delete is done when the RejectBulk command is sent

Release file locks and verify filesystem permissions.

Manually delete the file or send a reject bulk command again

maybe

Operating Questions

Question	Answer	Comments
Could happen in production?	Yes
Is it fatal?	No	The file may not be deleted, the actor will continue along its processing path

Question

Answer

Comments

Could happen in production?

Yes

Is it fatal?

The file may not be deleted, the actor will continue along its processing path

Logs

Log level Log message Also logs underlying exception?

Log level	Log message	Also logs underlying exception?
ERROR	`Error encountered deleting file {fileName}`	Yes

ERROR

Error encountered deleting file {fileName}

Yes

Resolution Notes

#	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 error could originate from a number of common I/O exceptions as it occurs from reading and writing files. The system event raised from this exception type should be triaged as any other I/O exception is treated by the client. Some issues could be (please note this is not an exhaustive list): storage availability storage space connectivity to file storage invalid read/write path permission issues
3	Delete the file	This can be done manually (e.g. by a human) or via a system developed by the client. An example of this process: retrieve the file name from the FileDeletionFailed system event delete the file
4	Trigger a BulkRejectedNotification notification	Call the Send method on your BulkNotificationPort spring bean, supply a BulkRejectedNotification as an argument

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 error could originate from a number of common I/O exceptions as it occurs from reading and writing files.

The system event raised from this exception type should be triaged as any other I/O exception is treated by the client.

Some issues could be (please note this is not an exhaustive list):

storage availability
storage space
connectivity to file storage
invalid read/write path
permission issues

Delete the file

This can be done manually (e.g. by a human) or via a system developed by the client.

An example of this process:

retrieve the file name from the FileDeletionFailed system event
delete the file

Trigger a BulkRejectedNotification notification

Call the Send method on your BulkNotificationPort spring bean, supply a BulkRejectedNotification as an argument