RootComponentGenerationFailed event
Highlight
| Event | Description | How to recover | Flow Related |
|---|---|---|---|
RootComponentGenerationFailed |
• 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 |
yes |
Operating Questions
| Question | Answer | Comments |
|---|---|---|
Could happen in production? |
Yes |
|
Is it fatal? |
Yes |
You will have to resolve this issue to process bulks |
Logs
There are no logs giving further information on this issue. The issue is flagged through the system event, and the bulk state is managed (i.e. it remains the same until) until a command is retried following resolution (see resolution steps section below)
| Log level | Log message | Also logs underlying exception? |
|---|---|---|
- |
- |
- |
Resolution Notes
Currently, the only RootComponentGenerationFailed system event raised is when finding the insertion points (i.e. when adding or updating a Component).
| # | Action | Comments |
|---|---|---|
1 |
Check the system event for underlying exception. |
The System Event contains the error in the errorMessage field. This is expected to be "Component content does not contain all insertion points defined in bulk specification". |
2 |
Compare the content of the component that is attempted to be bulked against the bulker configurations supplied to the application |
Look for discrepancies and either repair the component content or update the configuration |
3 |
If updating configuration, then restart the application to apply the updated config |
|
4 |
Resubmit the failing command |
You can do this through the client system by hitting the appropriate methods in the aggregate interfaces (i.e. BulkAggregate, RecurringBulkAggregate). |