Before you begin
- How Forge Data Connects
How it works
Follow the arrows from left to right. Each stage prepares the information the next stage needs.
- 01Recommended
Identify blocked action
If Product creation fails, check BOM coverage and Variant rules.
provides the information needed for - 02Recommended
Read exact message
If Routing creation fails, check active BOM, Stations, Repair Stations, and connectivity.
provides the information needed for - 03Recommended
Check immediate prerequisite
If Work Order creation fails, check Routing, active Line assignment, Shift, Product, and Variant.
provides the information needed for - 04Recommended
Check status and Plant
If release fails, check serial count, Starting Line, capacity, active BOM, inventory, and required identifiers.
provides the information needed for - 05Recommended
Correct
If an operation cannot complete, check current route, Station, required inputs, quality gates, and exception status.
provides the information needed for - 06Recommended
Retry
This stage contributes to the outcome: Start with the failing action and work backward through its dependencies.
Why this connection matters: Keep the exact error message; do not troubleshoot from memory.
Step-by-step in Forge
Navigation: The affected Forge module
- Open the failed record: Return to the Product, Routing, Work Order, Production Task, or shipment showing the error.
- Read the validation message: Expand the failed check and note the exact missing field, relationship, status, or quantity.
- Check prerequisites: Verify active BOM, Stations, Repair Stations, Shift, Line assignment, capacity, serials, inventory, and identifiers as applicable.
- Correct the source record: Open the linked configuration, make the required change, and select Save.
- Retry the action: Return to the original record and select Validate, Create, Release, or Complete again.
Watch the task
Watch: Troubleshooting Decision Tree
GIF walkthrough placeholder for Troubleshooting Decision Tree.
Rules to remember
- Keep the exact error message; do not troubleshoot from memory.
- Confirm the record belongs to the current Plant.
- Fix the earliest missing dependency instead of changing downstream data.
Ready when
- The blocked action is clearly identified.
- The immediate prerequisite has been checked.
- The correction is verified with the smallest safe retry.