Glossary
What is exception handling?
Exception handling is the governed path an automated workflow follows when something does not fit the rules: a payout that will not match, a stuck order, an integration error. Instead of failing silently or forcing a person to hunt, the exception is classified, routed to the right owner with context, and resolved with human approval where it matters.
The definition
Exception handling explained
Automation succeeds or fails on how it treats the cases that do not fit the happy path. A workflow that only handles clean records pushes every messy one back onto a person with no context. Good exception handling does the opposite: it catches the deviation, codes why it happened, and hands it to the right owner ready to act.
This is also where governance lives. Exceptions that carry money or risk (destructive retries, customer-impacting holds, out-of-policy credits) route to a human approval point rather than executing automatically. That discipline is what lets automation scale without quietly making decisions no one signed off on.
Where this shows up at Altura
FAQ
Frequently asked question
See also
Related terms
Related terms that come up in the same workflows.
01
Exception seam
An exception seam is a point in an operating process where the deterministic rules stop and a person starts hunting: a payout that will not tie out, an order held for a reason nobody recorded, a partner document that changed shape. The work is real, recurring, and usually invisible to the systems that report on it.
Read the definition02
Happy-path integration
A happy-path integration is the deterministic motion an integration platform already handles well: an order arrives, an item matches, a fulfillment posts, an invoice follows. Every input fits the rules and no judgment is required. It is the part of commerce operations that is genuinely solved, and it is not where the backlog lives.
Read the definition03
Celigo flow
A Celigo flow is a configured integration pipeline in the Celigo platform that moves data between systems, for example syncing orders from a storefront into NetSuite, on a schedule or in response to an event. Flows are where integration logic, error handling, and retries live for a NetSuite-centered operation.
Read the definition04
Settlement reconciliation
Settlement reconciliation is the process of proving that each marketplace remittance statement and payout deposit matches the underlying orders, refunds, fees, reserves, and adjustments in NetSuite. It is not the statement itself. It is not the bank transfer event; it is the governed matching workflow that explains variances before finance posts the close.
Read the definitionDealing with exception handling in your operation?
Tell us where the work breaks today, and we'll help scope the governed workflow worth converting first.