Bots - Pause button fails with 404 because it uses the controller name instead of the config name

[rapcmia]

Describe the bug

This issue was noticed while testing hummingbot/hummingbot-api#163 through the condor web dashboard. When the pause button was clicked for an active bot e.g bot_20260520035229-20260520-035250, the dashboard sent POST /controllers/bots/bot_20260520035229-20260520-035250/grid_strike/config and the API returned 404 Not Found ❌

03:58:44.883 POST /controllers/bots/bot_20260520035229-20260520-035250/grid_strike/config
INFO:     172.20.0.1:45490 - "POST /controllers/bots/bot_20260520035229-20260520-035250/grid_strike/config HTTP/1.1" 404 Not Found

The bot configuration is there, but the pause request is using the wrong name in the API path. The dashboard is sending the controller name, grid_strike, when it should be sending the bot config name, test01. Because of that, the pause
request fails with 404 Not Found even though the bot config exists and can be updated.

Steps to reproduce

1. Open the Condor web dashboard bot section for a running bot.
2. Use a bot where the controller name and config name are different. For example, controller_name is grid_strike but the config name is test01.
3. Click the pause button for that bot.
4. Observe that the request fails with 404 Not Found.
5. Check the bot configs and confirm the bot config exists.
6. Send the same request again using the config name, test01, instead of the controller name, grid_strike.
7. Observe that the update succeeds.

Attach required files

n/a

[cardosofede]

this is solved right?