Documentation for a newer release is available. View Latest

Esta página no está disponible actualmente en Español. Si lo necesita, póngase en contacto con el servicio de asistencia de Icon (correo electrónico)

ProduceBulkFileFailed Event

Highlight

Event	Description	How to recover	Flow Related
ProduceBulkFileFailed	• 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 bulk file	• Ensure sufficient space and permissions and connectivity to the component store, retry finalise command	no

Event

Description

How to recover

Flow Related

ProduceBulkFileFailed

• 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 bulk file

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

Operating Questions

Question	Answer	Comments
Could happen in production?	Yes
Is it fatal?	Yes	You will have to resolve this issue to process bulks

Question

Answer

Comments

Could happen in production?

Yes

Is it fatal?

Yes

You will have to resolve this issue to process bulks

Logs

Log level Log message Also logs underlying exception?

Log level	Log message	Also logs underlying exception?
ERROR	`Error encountered producing bulk file`	Yes

ERROR

Error encountered producing bulk file

Yes

Resolution Notes

# Action Comments

#	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	Resubmit the failing command	Once the underlying issue is resolved, resubmit the `FinaliseBulkCommand` to retry producing of the bulk file. You can achieve this in two ways: Option A: Via the Client System (Aggregate Interface) Call the `BulkAggregate.finaliseBulk` interface method with a `FinaliseBulkCommand` constructed using the same inputs as the original attempt. Option B: Via the Bulk Management REST API Call the `finaliseBulk` API endpoint using the original `bulkId`. Refer to the Bulk Management API documentation for endpoint details.

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

Resubmit the failing command

Once the underlying issue is resolved, resubmit the FinaliseBulkCommand to retry producing of the bulk file.

You can achieve this in two ways:

Option A: Via the Client System (Aggregate Interface)
Call the BulkAggregate.finaliseBulk interface method with a FinaliseBulkCommand constructed using the same inputs as the original attempt.
Option B: Via the Bulk Management REST API
Call the finaliseBulk API endpoint using the original bulkId.
Refer to the Bulk Management API documentation for endpoint details.