# \[Scheduled Extraction] A normal screen with no issues

<figure><img src="https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=-1086116399/https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FiKxoYELFf9WS8XCvYe6S%2Fblobs%2FVR8P9fl0k8NTbTIAaXRV%2Fscheduler-1.png" alt=""><figcaption></figcaption></figure>

This help guide is for the schedule feature **where repeated extraction has been set up** in a task, **when a page that was previously being extracted successfully** suddenly fails to extract. In the error screenshot **even though the target page appears normal** when data was not collected. This means that **the data location (structure) specified during initial setup has highly likely changed, or that area no longer exists**.In this case, we recommend reselecting the data on that page and registering it as a new task.

<figure><img src="https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=-213326703/https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FiKxoYELFf9WS8XCvYe6S%2Fblobs%2FZQniK6l6NHeEhcfuHvp3%2Fscheduler-2.png" alt=""><figcaption></figcaption></figure>

#### **✅ Solution** <a href="#solution" id="solution"></a>

**The selection methods described below are not recommendations for all cases**. This guide **when an existing extraction fails** is a reference tip to increase the success rate in a new task. For sites with simple structures, selecting multiple detailed areas can still collect data without issues.​

* Access the page, **reselect the data, and extract**. If you want to specify an area using Parts for extraction, selecting a slightly higher element (a larger area) can reduce the chance of failure during repeated extraction.

<figure><img src="https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=-1509943523/https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FiKxoYELFf9WS8XCvYe6S%2Fblobs%2FRfHQo2CYYZcKtLnAPST6%2Fscheduler-3.png" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**If the problem continues even after trying all the suggested methods, please contact us at** [**hello@listly.io**](mailto:hello@listly.io)**. We will help you resolve the issue after an accurate diagnosis of the cause.**
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.listly.io/support/solutions-by-extraction-error-message/scheduler-normal-screen.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.