ArchiveBulkFailed event

Highlight

Event Description How to recover Flow Related

ArchiveBulkFailed

• Emitted when archiving a produced bulk file fails (e.g., cannot move/copy to archive location, destination unavailable or permissions missing).

• Check archive storage availability and credentials/permissions.
• Verify path configuration and free space.

no

Operating Questions

Question Answer Comments

Could happen in production?

Yes

+

Is it fatal?

No

After the ArchiveBulkFailed system event is raised, the system will continue processing. The next step in the processing is to send a BulkArchivedNotification notification. This happens regardless of a ArchiveBulkFailed system event being raised

Logs

Log level Log message Also logs underlying exception?

ERROR

 
Error encountered archiving bulk

Yes

Resolution Notes

# Action Comments

1

Check system logs for underlying exception

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

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):

  1. storage availability

  2. storage space

  3. connectivity to file storage

  4. invalid read/write path

  5. permission issues

3

Archiving the file

To archive the file, you can copy the bulk file from the bulk file location to the archive location.

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

An example of this process could be:

  1. retrieve the file name from the ArchiveBulkFailed system event

  2. retrieve the bulk file from the designated bulk file output location via file name

  3. copy the bulk file into the designated archive location.

4

Trigger a BulkArchivedNotification notification

OR

Manually trigger the dependent behaviour

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

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

Gotcha’s

  • Manually replaying the ArchiveBulkCommand via the archiveBulk method on AkkaBulkAggregate instance will not work.

    • As per Bulk Aggregate docs, regardless of if archiving was successful, a BulkArchivedNotification will always be generated and the bulk state will move from FINALISED (pre-archive) to COMPLETE (post-archive).

    • The ArchiveBulkCommand is not supported for bulk in the COMPLETE state