Solution alerts and re-solving
Eclipse solves every punch pattern ahead of time, once per machine, part length, part width, and material gauge. When a solve can't produce a real answer, it records the reason instead of sending something wrong to the controller — so a setup problem surfaces as an alert on the office screen rather than as scrap on the floor.
This page covers what each failure means, who fixes it, and what makes Eclipse try again.
Where failures show up
| Surface | What you get |
|---|---|
| Punch pattern → Solutions tab | One row per machine and size, with the status, the flat view, and the diagnostic detail. This is where you diagnose. |
| Punching → Solutions (All Pattern Solutions) | Every solution in the system, with failed rows highlighted — the plant-wide sweep. |
| Alerts panel | A critical Solution failed alert naming the pattern and machine; clicking it opens the pattern. Available as a subscription under Solution Error. |
| Order detail | An alert on the order, and a red Pattern cell on the affected item. |
| Orders list and scheduling grids | A stamp icon whose tooltip carries the status. |
Most statuses are shown exactly as they are named internally — SegmentNotOnMachine, not
"Segment not on machine". The tables below are keyed by what you actually see on screen.
Setup problems
These are all fixable in Pro (or in Eclipse Classic), and each one is telling you a specific thing is missing.
| Status | What it means | Where to fix it |
|---|---|---|
ShapeNotOnMachine | The pattern uses a shape code this machine's shape table doesn't have. | Add the shape to the machine's shape table, correct the pattern's shape code, or fix the shape alias it resolves through. The detail lists the exact missing codes. |
SegmentNotOnMachine | A punch names a segment that is neither canonical (Web, FlangePlus, FlangeMinus) nor an alias on this machine. | Add the entry to the machine's segment alias table, or correct the pattern. The detail lists the names it couldn't resolve. |
FeatureGeometryNotFound | The pattern needs segment resolution, but the tooling has no usable profile dimensions for this machine — no tooling entry, or a zero Fin Width or Leg Height. | Fill in the tooling dimensions for that tooling code and machine. |
SegmentCorrectionNotFound | The machine has commissioned bend corrections, but this job's gauge, side, and bend direction don't resolve to one. | The Segments tab: add the tooling's direction rule, or commission the missing combination. See when a correction can't be resolved. Machines with no commissioned corrections never see this. |
PunchPatternInvalid | The pattern breaks a rule — a segment on a tool or macro punch, a Y reference that isn't valid under a segment, or one flange resolving to two different leg-height columns (usually two vendors' conventions mixed in one pattern). | Fix the pattern, or the alias entries it resolves through. The detail says which rule was broken. |
MachineMissingTool | The machine doesn't have the tool the pattern asks for. | Use a machine that has it, or add the tool to the machine. |
NoMachineShapeTable | The machine has no shape table at all. | Create one on the machine's Shape Table tab. |
PunchPatternNotFound | The order names a pattern that doesn't exist. | Fix the order, or create the pattern. |
PartPrintingPatternNotFound | Part-print shape injection is switched on for the machine, but the pattern it points at is missing. | The machine's Part Printing tab (in the Shape Table editor): fix the configuration, or create that pattern. |
ToolingCodePatternNotFound | A tooling code pattern rule matched this job's tooling code, but the pattern it adds no longer exists. Eclipse fails the solve rather than shipping parts missing punches the profile requires. | The machine's Tooling Code Patterns tab: point the rule at an existing pattern, or delete the rule. |
The solver ran but couldn't place the holes
These two mean the configuration is coherent — the machine simply can't make this part.
SolutionNotFound— no arrangement of this machine's presses, tools, and axes produces the pattern at this length and width. Common causes are holes closer together than the tooling allows, a position outside an axis's travel, or two punches that need the same press at once.NoPunches— the conversion produced nothing to punch, which usually means the part is too short for the pattern at this length.
Error means something failed unexpectedly rather than a setup problem; check the server
log or contact AMS support.
Statuses that are not problems
Not every status is a failure, and some appear routinely:
SolutionFound— solved and ready.Pending— queued, not solved yet. Normal right after a change; alerts for pending solutions wait a minute before appearing so ordinary churn stays quiet.SolutionNotNeededandPatternHasNoShapes— nothing to solve, because the pattern has no shape punches. Tool and macro punches go straight to the controller, so a tool-only pattern never needs a solution. The All Pattern Solutions page filters these out by default.
Diagnosing a failed row
Two tools on the pattern's Solutions tab, both of which work on failed rows:
- The flat view (the eye icon) draws what did resolve — on a failure it shows the machine-referenced holes that still worked, with the status and the detail underneath, or says plainly that nothing was drawable. Seeing which holes survived usually points straight at the punch that didn't.
- The diagnostic detail — the chevron at the end of a row expands the raw text the solve produced, listing the specific shape codes, segment names, or correction combinations that failed. The chevron only appears when there is detail to show.
When Eclipse re-solves
Cached solutions are invalidated and recomputed automatically. You never need to clear anything by hand:
| You do this | Eclipse re-solves |
|---|---|
| Save the machine's shape table | Every solution for that machine |
| Save the segment aliases | Every solution for that machine |
| Save direction rules or bend corrections (including applying the commissioning worksheet) | Every solution for that machine |
| Edit a tooling's Fin Width, Leg Height, or Leg Height 2 | Every solution for that machine — other tooling fields don't trigger it |
| Save the machine's Tooling Code Patterns | Every solution for that machine |
| Save the global Shape Aliases tab | Every pattern that uses one of those alias names |
| Save or delete a punch pattern | That pattern's solutions — plus every solution on a machine whose tooling code pattern rules point at it |
| Restore a machine configuration backup containing Segment Rules | Every solution for that machine |
| Change an order's material to a different gauge | That job's solutions |
Swapping an order to a different material of the same gauge deliberately keeps the existing solution — bend behavior follows thickness, not the material code, so there is nothing to recompute. Saving the shape geometry library doesn't re-solve anything either: it only affects drawings, never punched positions.
If you need to force the issue — after fixing something outside Eclipse, say — the order detail's overflow menu has Re-run Solutions, which re-queues that job's solutions.
Related
- Resolving the "Duplicate punch pattern" alert — a different alert with a different cause: the same pattern name existing twice in Eclipse Classic.