> For the complete documentation index, see [llms.txt](https://visi-digital-internasional.gitbook.io/geo-prospector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visi-digital-internasional.gitbook.io/geo-prospector/geo-prospector-id/alur-kerja-prospeksi/data-delay.md).

# Penundaan data

Data Delay mengontrol ritme penjelajahan dan pengumpulan otomatis.

## Pilih pengaturan yang lebih aman saat

* Koneksi internet Anda tidak tidak stabil
* Targetnya besar
* Beberapa kategori dipilih
* Email Finder diaktifkan
* Halaman sumber merespons dengan lambat

## Pilih pengaturan yang lebih cepat dengan hati-hati

Pengaturan yang lebih cepat dapat mengurangi durasi pekerjaan, tetapi kestabilannya bergantung pada kondisi jaringan dan perilaku sumber. Alur kerja produksi harus memprioritaskan kelengkapan dan keterulangan daripada kecepatan maksimum.


---

# 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 dynamically by asking a question.

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

```
GET https://visi-digital-internasional.gitbook.io/geo-prospector/geo-prospector-id/alur-kerja-prospeksi/data-delay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.