> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix a problem

> Check connections, recover interrupted tasks and report reproducible faults.

<h2 id="connection-problems">
  1\. Connection problems
</h2>

<span id="connection-problems-overview" />

Check the supported version, required components, running application, and intended document.

Follow the connection-specific recovery steps. Confirm the target again before resuming the task.

For help understanding the setup or connection workflow, search the [Community forum](/help/get-help#community-forum) first. Include the application and version, connection state and steps you tried. If the connection still fails reproducibly, use [Report a problem](/studio-reference/ui-support#problem-reports) to send the relevant diagnostics.

<h2 id="interrupted-tasks">
  2\. Interrupted tasks
</h2>

<span id="interrupted-tasks-overview" />

Inspect the current result before retrying. Identify what completed, what changed, and what remains unfinished.

Use the appropriate recovery action and narrow the next request to the unresolved part where possible.

For advice on the workflow or how to improve the request, search the [Community forum](/help/get-help#community-forum) first. Describe the intended result, what completed and what you tried next. If the same fault can be reproduced, use [Report a problem](/studio-reference/ui-support#problem-reports) for the error and diagnostics.

<h2 id="report-an-issue">
  3\. Report an issue
</h2>

<span id="report-an-issue-overview" />

For a general question about how to use Ideatura, start with the [Community forum](/help/get-help#community-forum). Use [Report a problem](/studio-reference/ui-support#problem-reports) for a reproducible fault and its diagnostics.

Include the automation or chat, Chat ID, project/model, view/sheet, expected result, and what actually happened. These details let the team locate the same task and compare the intended and observed behavior.

Also include the Studio version, connected application/version, relevant error, and the smallest example that reproduces the issue. Review the report’s attachments and privacy information before submitting.

<span id="report-an-issue-in-ideatura" />

1. Copy the conversation or automation reference and Chat ID.
2. Name the model and view or sheet.
3. Write expected versus actual behavior.
4. Add a screenshot, report or permitted sample where useful.

<span id="report-an-issue-check-the-result" />

Someone can locate the task and reproduce the difference without guessing the target or request.

<h2 id="diagnose-before-retrying">
  4\. Diagnose before retrying
</h2>

Separate account entitlement, connection, missing inputs, unsupported operations, native dialogs and product errors. An empty library may be a workspace mismatch; zero credits may be an account issue; slow execution may be host work rather than AI reasoning. Record the exact state before changing settings.

If a run stops, inspect what already changed before rerunning. After repeated attempts with no useful progress, preserve the last accepted result and [report the problem](/studio-reference/ui-support#problem-reports). Include exact error, versions, target, expected/actual output and task identity. Do not assume every failure is caused by the prompt or the model.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.