factory troubleshooting

Start with the current factory and the affected resource:

islo factory current
islo factory machine get <machine-name>
islo factory line get <line-name>
islo factory line-run status <run-id>
islo factory line-run events <run-id>

Symptom	Check
A suggestion returns `machine_required` or `machine_build_failed`	Create and verify a Machine, then retry deployment.
A suggestion returns `integration_missing`	Connect the provider named in the response.
A suggestion returns `agent_name_conflict` or `line_name_conflict`	Rename or remove the conflicting resource, or deploy into another factory.
A Line manifest returns 422	Compare its fields with `islo schema factory --short`; check the referenced Agents with `islo schema agent`.
A trigger fires without a run	Check `islo factory triggers list --with-status`, `islo factory trigger-events list`, and the Line’s selector.
A stage fails	Inspect the Line run’s status and events to find the failed stage and its error.
A run cannot be steered	Stop the active run first; `stop` parks it.
A run reaches its usage or iteration limit	Inspect status, then steer with the relevant reset flag if more work is intended.

For CLI authentication and direct sandbox failures, use CLI troubleshooting. For environment components, read the Machine’s latest build and verification report.