You can analyze errors and fix retry data in bulk using Celigo Ora from within Error Management. This article covers how to access Ora from the Errors list view, use Ora to analyze individual errors, and apply fixes across multiple errors in a flow step.
Ora is currently in BETA mode and can make mistakes. Always review changes before approving them.
You must have errors to use Error Management. Learn more about:
Click Ora () to access it from within Error Management via the Errors list view.
Note the following when using the Ora icon in the Errors list view.
Warning
To analyze a single error, click the Ora icon () associated with that error. Don't select multiple errors and click the icon — Ora only uses the error associated with the icon you click. To apply a fix across multiple errors in a step, use the bulk retry data fix instead (see below).
After clicking Ora (), a prompt is pre-loaded automatically. It overrides any existing draft prompts you might have created.
Ora analyzes your error and provides:
-
a summary of what went wrong
-
likely root causes
-
step-by-step recommended actions
-
best practices
-
links to relevant documentation
Ora doesn't modify raw error messages or auto-apply recommended actions. Corrected retry data is always staged for your review before anything is applied.
You can ask Ora to fix retry data across all matching errors in a flow step using a plain-language description. Supported operations include replacing a value, setting a field, copying a value from another field, and removing line items.
To fix retry data:
-
In the Errors list view, click the Ora icon (
) for any error in the step you want to fix.
-
Describe the fix in plain language. For example: Replace 296026139 with 91967422740 in these errors and retry.
-
Ora validates the fix against a sample of actual failed records before staging anything.
-
Review the staged corrections in the UI and accept each one to apply it.
Note
Staged fixes currently require accepting each error individually. An "Accept all" option is not yet available.
Note
Selecting errors via checkbox does not pass those IDs to Ora. To target a specific subset of errors, tag them first, then instruct Ora to filter by that tag. For example: Find all errors tagged 'apple' and update retry data to replace X with Y. This limitation is temporary and will be updated when resolved.
Ora doesn't:
-
Assume or guess — it explicitly signals uncertainty and may recommend contacting Support instead.
-
Directly change flows, mappings, scripts, connections, or external systems. All changes require your approval.
-
Modify raw error fields used by classification/alerting.
-
Leak content across accounts or flow steps.
-
Stage and apply bulk retry data fixes without your approval. Corrected records are always presented for review first.
-
Respond to checkbox selections in the Errors list view. To target a specific subset of errors, tag them first and instruct Ora to filter by that tag. This limitation is temporary.