See what happened to an order
You found the order — now you want the story: what was in it, where it went, where it stopped, and why. Nodinite shows you the order's content in a readable format, the path it took, and any error along the way, so you can answer the customer or hand a precise description to whoever needs to fix it.
- ✅ Read the order the way your business sees it, not as raw XML or JSON
- ✅ See where and when the order stalled, and the error text if it failed
- ✅ Leave a comment so colleagues see what you found
When you need this
The customer says the order is wrong, or missing, or late. You have the order in front of you in a Log View (see Find an order by Order Id) and need to know what actually happened.
What you need
- The order's row in your Log View.
- Some of the buttons below appear only if your Role allows them — for example viewing the message body, or resending. If a button isn't there, your administrator hasn't enabled it for you.
Do it
- On the order's row, click the Action button and choose View details. The full Log Event opens in a new tab with everything Nodinite knows about it.
Example of the Action menu on a Log View row. - To read the order itself, choose View message using a Stylesheet. Your administrator can define a Stylesheet that presents the order as a readable document — order lines, customer, totals — instead of raw data.
Example of an order presented with a Stylesheet.
If no Stylesheet is available, View message body shows the raw content. - To see the path the order took, use the Timeline (the timeline icon in the header when the Log View is grouped by order). It shows each step in time order, so a gap or a stop stands out.
Example of a timeline for one order across several systems. - If a step failed, the event's details show the error. For errors logged from .NET applications, Nodinite formats the whole error chain so the outermost message — usually the business-friendly one — is easy to read; see View Exception Details.
- Found something worth sharing? Open the Comments tab in the details panel and add a comment. Comments stay with the event permanently, so the next person sees your findings.
Example of the Comments tab on a Log Event.
What you'll see
The details page has tabs: the event summary, the Search Fields your administrator extracted (Order Id, customer, amount…), any Additional Fields, technical Context Properties, the Repository Model tab showing which service and contract the event belongs to, and Comments. Business users mostly need the summary, the Stylesheet view, and the Timeline; the rest is there when IT asks.
Example of the tabs available on a Log Event's details.
If it doesn't work
- No "View message using a Stylesheet": either no Stylesheet is defined for this message type yet, or your role can't use it. Ask your administrator; they configure Stylesheets.
- No Timeline icon: the Log View isn't grouped by order. Your administrator can group it — see Working with Log Views.
- The order needs to be sent again: if your role allows it, Resend is in the details page. If not, add a comment describing what you found and contact Support or your integration team.