"Problem orders" is a separate section with a list of orders that have the problem flag set. An order becomes problematic automatically (XNC error, material shortage, processing error) or manually by a manager with a stated reason. Open it from "Orders → Order with a problem".
Where the problem flag comes from
- Automatically — the system sets the flag on critical errors: invalid XNC, no material in stock, cutting-card generation failure.
- Manually — the manager or workshop foreman opens "Mark as problem" in the order card and provides a reason.
What the section shows
The list contains: ID, external code, name, customer, manager, problem reason, flag-set date, person responsible for resolution, current order status. Row colour-coding depends on problem age (yellow → red).
Actions on a problem order
- Assign a responsible person — who handles the problem.
- Leave a comment — what was found out, what is planned.
- Clear the problem flag — once the cause is fixed; the order returns to "Current".
- Cancel the order — if the problem cannot be resolved.
- Block the order — pause status progression until a decision is made.
What the factory admin should know
- A blocked order does not move through statuses automatically and is not included in production tasks.
- All comments and actions are logged in the order history — you can see who did what and when.
- Problems older than N days (configurable) are highlighted in red and appear in the daily report for the supervisor.
Related topics
- Order card — where to set/clear the problem flag.
- Order statuses and lifecycle — how blocking affects the status.
- CRM — section overview.