diff --git a/docs/telegram-usage.md b/docs/telegram-usage.md index b4817b4c3..3ed44d123 100644 --- a/docs/telegram-usage.md +++ b/docs/telegram-usage.md @@ -200,9 +200,8 @@ official commands. You can ask at any moment for help with `/help`. |----------|-------------| | **System commands** | `/start` | Starts the trader -| `/pause` | Pause the trader. Gracefully handle open trades according to their rules. Do not enter new positions. +| `/pause | /stopbuy | /stopentry` | Pause the trader. Gracefully handle open trades according to their rules. Do not enter new positions. | `/stop` | Stops the trader -| `/stopbuy | /stopentry` | Stops the trader from opening new trades. Gracefully closes open trades according to their rules. | `/reload_config` | Reloads the configuration file | `/show_config` | Shows part of the current configuration with relevant settings to operation | `/logs [limit]` | Show last log messages. @@ -251,7 +250,7 @@ Below, example of Telegram message you will receive for each command. > **Status:** `running` -### /pause +### /pause | /stopentry | /stopbuy > **Status:** `paused, no more entries will occur from now. Run /start to enable entries.` @@ -259,22 +258,18 @@ Prevents the bot from opening new trades by changing the state to `paused`. Open trades will continue to be managed according to their regular rules (ROI/exit signals, stop-loss, etc.). Note that position adjustment remains active, but only on the exit side—meaning that when the bot is `paused`, it can only reduce the position size of open trades. -### /stop - -> `Stopping trader ...` -> **Status:** `stopped` - -### /stopbuy - -Alias of the `/pause` command. - After this, give the bot time to close off open trades (can be checked via `/status table`). -Once all positions are sold, run `/stop` to completely stop the bot. +Once all positions are closed, run `/stop` to completely stop the bot. `/start` resume the bot to the `running` state, allowing it to open new positions while handling existing ones. !!! Warning - The stop-buy signal is ONLY active while the bot is running, and is not persisted anyway, so restarting the bot will cause this to reset. + The pause/stopentry signal is ONLY active while the bot is running, and is not persisted anyway, so restarting the bot will cause this to reset. + +### /stop + +> `Stopping trader ...` +> **Status:** `stopped` ### /status