Troubleshooting

2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

/deepline-gtm Diagnose this Deepline failure in the environment where it happened. Separate installation, workspace authorization, provider access, invalid input, execution, usage, and destination errors. Inspect existing work before retrying. Explain which check failed, what evidence supports that conclusion, and the smallest next action. Do not interpret a timeout as no work, missing usage as zero, or an access failure as an empty result.

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

3. Review the result

The report names the failed boundary and preserves uncertainty where evidence is missing. It gives a recovery action rather than a new execution with unexplained duplicate risk.

Ask your agent:

/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.

Approve a larger job, recurring work, or external changes only after reviewing that decision.

No. Preserve the original execution identity and investigate its outcome. The request may have completed even though the response was lost.

How-to guides

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

​1. Have your context ready

​2. Ask your agent

​3. Review the result

​Check your understanding

​Related guides

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

Related guides