> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/troubleshooting/integration-issues/failed-to-fetch-error.md).

# How to analyze the "Network error: Failed to fetch" in the Execution panel

Learn how to investigate the issue when fetch failures occur in the Execution panel.

For executions in the [Execution panel](/documentation/development-cycle/build-overview/canvas/execution-panel.md) on Canvas, the system waits up to 60 seconds for a response. If no response is received within this time, a "Failed to fetch" error is displayed. However, the execution continues in the background and can be reviewed in the **Logs** page.

To review the execution:

1. Go to the **Monitor** page.
2. Click **Pipeline Logs**.
3. Use the **Pipeline Name** filter to locate the execution.

{% hint style="info" %}
You can also analyze the execution on the Monitor page if you lose your internet connection.
{% endhint %}

For slightly longer executions, the pipeline continues running for up to 5 minutes. 

If your pipeline is focused on long executions, take a look at our documentation on [Pipeline executions](/documentation/development-cycle/dashboards/alerts/available-metrics.md#pipeline-executions). 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/troubleshooting/integration-issues/failed-to-fetch-error.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.