What actually runs
Lesson 19 of 25 7 min read
Ask Supply Lens which map or profile will run for a message, see how it was assembled, and see who wrote each part.
With shared bases, organisation definitions and overlays, the honest answer to "what does this customer run?" can be a chain of several pieces. What actually runs gives you that answer directly. It is the single most useful troubleshooting screen in this course.
Ask the question
- On the organisation's Maps & Profiles overview, select What actually runs.
- Select the Kind, Integration type and Document type.
- Optional: to ask about one integration, select it in Integration. The list shows the organisation's integrations of the selected type.
- Select Resolve.
Read the result
| Part | What it shows |
|---|---|
| The composed body | The body that runs, as a Tree or as JSON. |
| How it was assembled | The root and each overlay on it, from the root outwards. Select one to open it. |
| Who wrote each node | Which part of the body came from the root, and which from each overlay. |
The tree uses the same chips as End result: plain for the root, solid where an overlay changed a node, outlined where it changed something inside. To see only the nodes an overlay changed, turn on Only overlay changes above the Who wrote each node table.
What it does not show
- Drafts. Drafts are never used, so they never show here. If you expected your change and do not see it, check it is published.
- Nothing published. If there is nothing published for that kind, integration type and document type, you see Nothing is configured for that.
- A broken chain. If something is configured but an overlay no longer fits its base, you see Something is configured, but its chain no longer composes, so nothing would run.
Use this, not the Modules tab Preview
For a config-driven type, the Preview on the integration type's Modules tab shows No route matches. That is expected: it only looks at module routes and cannot see published maps and profiles. Always use What actually runs for config-driven types.
Why ask about one integration?
Supply Lens supports maps and profiles scoped to one integration, which win over the organisation's. You cannot create those on these screens, but they can exist. Selecting the Integration gives you the answer for that exact integration, including anything scoped to it.
The log names what ran
The developer notes say each run also writes a line to the integration's log naming the map or profile that ran, its version, its scope and the chain it was composed from. If a customer asks what ran for one particular Document, rather than what would run now, ask a developer to check that line.
Proving Hilltop's express overlay is live
After publishing Acme orders: express, you open What actually runs, choose Create map, Acme API and warehouse orders, and select Resolve. How it was assembled shows Acme orders v1 (shared base) then Acme orders: express v1. With Only overlay changes on, Who wrote each node lists one row: order.priority, written by the overlay. You paste a screenshot into the ticket as evidence and close it.
Recap
- What actually runs resolves kind, integration type, document type and optionally one integration.
- It shows the composed body, how it was assembled, and who wrote each node.
- Only overlay changes filters to what overlays changed.
- Nothing is configured for that. means nothing published; a chain that no longer composes means an overlay needs fixing.
- For config-driven types, use this rather than the Modules tab Preview.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.