Find why a map or profile does not run
Lesson 23 of 25 6 min read
A step-by-step method for when the map or profile you expect is not doing the work.
"I published it, but nothing happened" is the support ticket you will see most. There are only a handful of causes, and you can check them in order. In this lesson you will learn that order and practise it.
The method
1. Use What actually runs
Choose the kind, integration type and document type, and the integration if you are asking about one. This tells you what Supply Lens would use right now.
2. Nothing is configured
If it shows Nothing is configured for that., nothing is published for that kind, integration type and document type. Publish one. Remember, a draft is never used, however finished it looks.
3. The chain does not compose
If it shows that the chain no longer composes, an overlay does not fit its base, for example because a new base version removed a node the overlay targets. Correct the overlay. End result on the overlay helps you see where.
4. The right one, but no messages
If the correct map or profile runs but no messages arrive, look at the routing of the integration type: Administration → Integrations → Integration Types, then the Routing tab. A row that is Not routed loses its messages; a row that is Off gives the reason. The course Message routing and modules in Prism covers this in detail.
5. The right one, and messages fail
The developer notes describe the message a customer sees when a create or parse map fails while running: it names the node that failed, and on a line, the line number, for example Line 3: Required expression produced no value. That node id is your starting point: find it in What actually runs, see which level wrote it, and take it to whoever owns that level.
Three tickets, three causes
- Riverside Teas: "Our new Acme map isn't used." What actually runs shows the shared base. Riverside's map is in the list as Draft. Cause: never published.
- Hilltop Coffee: "No Northbank orders since this morning." What actually runs shows Hilltop's create map v2, correct. On the Northbank WMS Routing tab, Create shows Off: the route is switched off. Someone paused it. Cause: routing.
- Moorland Candles: "Orders failing since the release." What actually runs says the chain no longer composes. Moorland's carrier overlay targets a node the new base renamed. Cause: overlay needs fixing.
Recap
- Always start with What actually runs.
- Nothing configured: publish one; drafts never count.
- Chain does not compose: fix the overlay.
- Right definition but no messages: check the type's routing.
- Right definition but failures: start from the node id in the error message.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.