---
title: "Task-Polling Intervals"
slug: "task-polling-intervals"
updated: 2024-09-17T12:39:47Z
published: 2024-09-17T12:39:47Z
canonical: "help.hyperscience.ai/task-polling-intervals"
---

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

# Task-Polling Intervals

In v30, we introduced the *SDM_BLOCKS_TASK_POLL_INTERVAL* ".env" file variable, which gives you more control over your instance's task-polling intervals and, in turn, your overall submission throughput.

In a flow, each block includes multiple tasks. The *SDM_BLOCKS_TASK_POLL_INTERVAL* variable determines how often the system polls for these tasks. The value you enter is the number of seconds that pass between polling attempts. This value should be an integer greater than or equal to 1.

```plaintext
SDM_BLOCKS_TASK_POLL_INTERVAL=
<number_of_seconds_between_block-task_polling_attempts>
```

- In TVE environments, the default value is *1*.
- In Production environments, the default value is *10*.

In general, the fewer submissions you expect to process in an environment, and the fewer VMs an environment has, the lower the value should be. This recommendation is based on the overall task-polling behavior of the system.

The system automatically polls for tasks after a task is completed, regardless of the value of *SDM_BLOCKS_TASK_POLL_INTERVAL*. Therefore, in environments that process a high volume of submissions—and have a continuous backlog of tasks—a higher value does not impact the speed at which the system processes submissions. In contrast, environments that process a small number of submissions complete tasks less frequently. In these environments, the system has a limited backlog of tasks to draw from, and a higher *SDM_BLOCKS_TASK_POLL_INTERVAL* value can cause delays in processing.