> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.islo.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.islo.dev/_mcp/server.

# factory troubleshooting

> Diagnose factory deployment, trigger, Machine, and run failures.

Start with the current factory and the affected resource:

```bash
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](/concepts/machines), 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](/cli/troubleshooting). For environment components, read the Machine's latest build and [verification report](/concepts/machines).