> For the complete documentation index, see [llms.txt](https://docs.itradingbot.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itradingbot.net/en/binance-robot/binance-editing-tasks.md).

# Binance: editing tasks

<mark style="color:$tint;">On the Binance robot page, you can change one task or apply general parameters to selected tasks. The instructions are for a table list of tasks; check the selected robot and the presence of active transactions before you edit.</mark>

### Change one of the tasks

1. <mark style="color:$tint;">Open up the</mark> [<mark style="color:$tint;">Binance robot</mark>](https://app.itradingbot.net/binance-robot) <mark style="color:$tint;">and select the connection you need.</mark>
2. <mark style="color:$tint;">Find the task in the table. Click on its name or open the edit through the line menu.</mark>
3. <mark style="color:$tint;">Check the asset, the direction, the volume, the grid and the exit method. For the signal task, also check the entry, filter and exit conditions on the signal.</mark>
4. <mark style="color:$tint;">Change the fields you want and click Change task.</mark>
5. <mark style="color:$tint;">Wait for the answer, then check the saved values in the table. If necessary, reopen the constructor.</mark>

<mark style="color:$tint;">The current task is kept in the editing mode. Description of fields in the article Binance: parameters of the task. —</mark> [<mark style="color:$tint;">Binance: the parameters of the task</mark>](/en/binance-robot/binance-task-parameters.md)

### Consider the active trade

<mark style="color:$tint;">The table lists the task line with the active trade, and the editing is not available. Wait for the trade to be completed and the task update. Turning off the task or taking the signal off the calculation does not in itself confirm the position closing.</mark>

<mark style="color:$tint;">The stored grid parameters are applied to the next cycle. The already running cycle continues to use the parameters with which it was started; the storage does not rebuild its order. Changing the number of cycles in the settings is valid for a new start and does not change the number of cycles left in the already running series.</mark>

<mark style="color:$tint;">The actions on the current trade are described separately in the article</mark> [<mark style="color:$tint;">Binance: robot tasks and active trades</mark>](/en/binance-robot/binance-robot-tasks-and-active-trades.md)<mark style="color:$tint;">. Changing the configuration of the task is not a trade closing command.</mark>

### Change some of the tasks

<mark style="color:$tint;">For group correction, select at least two tasks with the same signal type and one group of assets in the calculation currency. For example, the tasks USDT and USDC are edited by separate groups. Excluded tasks with active trades: they block group editing.</mark>

1. <mark style="color:$tint;">Mark the lines and check the task counter. After the filter is changed, some of the marked lines may be outside the visible list.</mark>
2. <mark style="color:$tint;">Select Select to change or edit ISignal Availability depends on the sample.</mark>
3. <mark style="color:$tint;">Check the common fields. The corresponding values are filled; the field with different values remains empty.</mark>
4. <mark style="color:$tint;">Just enter the parameters you want to change for the whole group. The untouched fields retain the same values as the previous tasks. An empty common field does not mean a parameter is zero.</mark>
5. <mark style="color:$tint;">Click Change tasks and check the result for the selected lines.</mark>

<mark style="color:$tint;">For general correction, the ISignal signal tasks selected must match the indicator and filter settings; trading pairs may differ. The changed set of conditions applies to the entire selected group.</mark>

### Check the result after the error

<mark style="color:$tint;">If some of the changes are rejected or the answer is not received, update the list and compare the parameters for each task involved. A group action error does not confirm that the entire set has remained unchanged. Re-send only the changes that are still needed.</mark>