Error fixInfor OS / IONION Desk / Document Flows

Diagnose and fix a failed BOD document flow in ION Desk

Error

ion document flow failed error in ion desk

Also searched as

infor ion bod validation error
document flow status failed ion desk
how to fix failed bod in infor ion
ion desk message tracking error

Short answer

A Document Flow showing Failed in ION Desk means a BOD (Business Object Document) stopped either at schema validation, at the mapping step, or at the target application. Open the failed instance's detail to see the exact failing element, fix the source data or mapping, then use Resubmit rather than re-triggering the original transaction to avoid duplicates.

Applies to: Infor OS Portal, ION Desk / ION Workbench, tenants integrating CloudSuite apps via BODs

Diagnose and resubmit a failed BOD in ION Desk

1Open ION Desk (ION Workbench in some CloudSuite tenants) and go to Monitor > Document Flows.
2Filter by Status = Failed and by the Document Flow that owns the failing integration, for example the flow connecting a CloudSuite app to a non-Infor system.
3Click into the failed instance to open the Document Flow Detail and check the timeline for the node - Connection Point, Map, or target app - where it stopped.
4Open the Error tab or the raw message content to read the exception text. Schema validation failures usually name the missing or malformed Noun element, for example a required DocumentID or amount field being blank.
5Compare the payload against the mapping configured in ION Desk > Connect > Document Flows > the flow > Map, and check whether a source field is empty, was renamed upstream, or the map version does not match the target app's current BOD version.
6Fix the root cause in the source data, the map, or the target endpoint, then use Resubmit (or Republish) on the failed message rather than re-running the original source transaction, to avoid duplicate postings.
7If failures repeat for the same flow, check Connection Point health under ION Desk > Connect > Connection Points for downtime, certificate, or authentication problems on the target system.
8After a target app version upgrade, check whether the BOD version it subscribes to changed and whether the Document Flow needs remapping before resubmitting a batch of failures.

What a Document Flow actually is

ION integrates applications through Business Object Documents - standardized XML messages, built on the OAGIS model, that represent a business event such as a sales order, a GL journal, or a shipment. A publishing app sends a BOD Noun/Verb combination onto ION, and one or more Document Flows route, optionally map, and deliver it to subscribing apps. Monitor > Document Flows in ION Desk shows every instance of that routing, including ones that stopped partway through.

Because the flow can fail at different stages - inbound validation, the mapping transform, or delivery to the target - the same word Failed can mean very different root causes, which is why the detail view matters more than the summary list.

Reading the failure detail correctly

Open the failed instance rather than trusting the flow-level status alone. The History or Timeline panel shows which node the message reached before it stopped, and the Error tab (or raw message viewer) usually includes the actual exception text from the failing component, not just Failed. For schema validation errors this text names the specific Noun element that was missing, blank, or malformed.

Schema validation vs mapping vs endpoint failures

Schema validation failures happen before any mapping runs and point to bad or incomplete source data - a required field left blank in the source transaction. Mapping failures happen when the configured Document Flow Map expects a source field that is missing, renamed, or structured differently than the map assumes, often after a source app customization. Endpoint failures happen after a valid, correctly mapped BOD is ready to deliver, but the target Connection Point is unreachable, unauthenticated, or rejecting the payload for its own business-rule reasons - these look identical to the first two in the flow list but show a completely different Error tab.

Resubmitting safely

For financial and transactional BODs, resist the temptation to just re-run the original transaction in the source app after a failure - if the first attempt partially succeeded downstream, that can create a duplicate GL entry, order, or shipment. The safer path is fixing the underlying cause and using ION Desk's own Resubmit on the failed message, which replays the same BOD instance instead of generating a new one.

Common pitfalls

!Manually re-running the source transaction instead of using Resubmit, causing duplicate GL entries or duplicate orders downstream.
!Ignoring a mapping warning on a field that looks optional in the BOD schema but that a downstream custom map actually depends on.
!Assuming a Failed flow is a code bug when the target application is simply down or in maintenance.
!Not checking Document Flow and map versioning after a source or target app upgrade changed the BOD schema.
!Letting failed messages queue up unmonitored until there are hundreds of unresolved Failed flows and no clear starting point.
!Resubmitting a batch of failures without first confirming the same root cause applies to all of them.

How an ERP-grounded AI assistant handles this

For document flow failures, ERPray can watch Message Tracking, pull the Error tab text from a failed BOD, and cross-reference it against the flow's map history so it can tell an admin whether the pattern behind a batch of failures is a recent mapping change, a source data gap, or a target outage - the same triage work a Document Flow admin does today, just done in seconds across many failed instances instead of one click at a time. It surfaces flows worth a human review rather than auto-resubmitting financial transactions on its own.

See ERPray

Frequently asked questions

Where do I see failed BODs in Infor OS?

In ION Desk (or ION Workbench on older tenants) under Monitor > Document Flows, filtered by Status = Failed. Click into an instance for the detailed timeline and error text rather than reading the summary list alone.

What does Document Flow mean in ION terms?

A configured route that takes a published BOD from a source application, optionally transforms it through a map, and delivers it to one or more subscribing applications or external Connection Points. Monitor screens in ION Desk show every instance of that route running.

Can I edit and resend a failed BOD payload?

ION Desk lets you Resubmit a failed message after the underlying cause (source data, mapping, or endpoint) is fixed, replaying the original instance rather than creating a new transaction, which avoids duplicate postings in downstream systems.

Why do document flows fail right after an app upgrade?

An upgraded source or target application can change the BOD version or the fields it populates. If the Document Flow's mapping was built against the old version, previously working flows start failing schema validation or mapping until the map is updated.

Error fix

Fix a 401 Unauthorized error from Infor ION API

A 401 from ION API almost always means the credentials in the .ionapi file no longer match what ION API Gateway expects - not that the password is simply wrong. Check whether the Authorized App or service account behind the file was revoked, regenerated, expired, or issued for a different tenant, then re-test with a direct OAuth2 client_credentials call before touching any calling code.

How-to

How to query Infor Data Lake with Compass SQL

Compass is the SQL query layer in Infor OS for querying Infor Data Lake, where flattened copies of BODs published over ION are stored by Noun and Verb. Open a Compass SQL Workbench tab, browse the schema for the correct table, and run a filtered SELECT rather than pulling the full history, since Data Lake tables can hold years of append-only data.

Error fix

Fix a Ming.le homepage widget that will not load

A blank or endlessly spinning Ming.le widget is usually a permissions, session, or backend availability problem, not a broken widget itself. Confirm the issue is widget-specific, check the user's Security Group access to the underlying app, and look at the widget's network calls in browser dev tools to see whether it is failing with 401/403 or simply timing out against a down service.

How-to

Connect a Birst Space to Infor Data Lake and build a report

Birst is Infor's embedded BI layer, and the recommended way to report on live Data Lake data is a Live Access source inside a Birst Space rather than a static upload. Build the logical model over a filtered set of tables, apply row-level security, and publish the dashboard to a Ming.le homepage so users reach it without leaving Infor OS.

AI for ERP

AI Agents Over Infor ION API, BODs, and the Infor Data Lake

Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.