Bulker Events and recovery

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.

Retry the archive command

Emitted when an invalid bulk configuration results in failure (e.g. during bulk creation/opening or validation).

Fix the bulk specification (unsupported parser, invalid settings).

Restart the application and retry the add component command

Emitted when a command sent to the bulk aggregate fails validation (e.g. missing content, invalid path, parent doesn’t exist, unsupported in the current state).

Correct the command payload or sequencing (ensure the parent exists, valid path, content provided).

Send a different or corrected command appropriate to the current bulk state.

Emitted when deletion of a component from the component store/database fails after a valid remove request.

Inspect component store availability and logs.

Resolve storage issue (locks/connectivity) and retry the delete operation.

Emitted when saving component(s) to the component store/database fails after a valid add/update request.

Check database availability and constraint violations.

Resolve the persistence issue and retry the save (re-send the add/update command if needed).

Emitted when loading the bulk state (e.g., from the state store) fails.

Verify state store connectivity and credentials.

Restart the application after resolving the persistence issue; if transient, a backoff retry should recover.

Emitted when persisting/storing the bulk state fails.

Check state store health and disk space.

Restart application after resolving persistence issue; Apply retries with backoff; ensure idempotency of state changes.

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

Release file locks and verify filesystem permissions.

Manually delete the file or send a reject bulk command again

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

Emitted when producing/assembling the bulk output file fails (e.g. merge/write errors, disk space, template issues)

Unable to retrieve components while trying to produce a bulk file

Ensure sufficient space and permissions and connectivity to the component store, retry finalise command

Emitted when generation of the root component fails during bulk creation/opening (e.g. missing parser/invalid template).

Component content does not contain all insertion points in specification

Verify content and markers are aligned to bulker configuration and retry the add component command

Emitted when scheduling auto-close for bulk fails.

Exception occurred while attempting to schedule auto close

Verify autoclose configuration e.g. cron syntax restart application to refresh configuration

Emitted when deleting a bulk state from the state store/database fails (e.g. post-completion clean-up cannot remove the record).

Check state store permissions and connectivity.

Retry the terminate command