Archival in V2 bot reappear

Bug Reports
1

Note: Before posting a bug, please check the bot’s event logs for possible errors and double-check that the bot configuration should have allowed the expected action (e.g., checking price filters, indicator conditions, etc.).

Bug details:

  • Bot URL → Not a bot problem
  • [Optional] Steps to reproduce →
  • Expected result → An archived bot is always shown back after a full refresh in v2. You can archive it again but it will reappear once the website is fully refreshed.
2

Thanks for the report, and for confirming it’s a general behavior rather than a single bot — that helps.

To reproduce this on my side, a couple of quick details:

  1. Which bot type is this? (DCA / Combo / Grid)
  2. When you archive, does the bot disappear immediately and only come back after a full page refresh (F5 / reload), or does it come back on any navigation/tab switch?
  3. Are you archiving from the main bots list, or from inside the bot’s own page?

Once I have that I’ll reproduce it in v2 and dig into whether the archive state is failing to persist server-side. Thanks!

3

I have seen it for hedge combo bot. After an F5 it doesn’t come back, you need something like logout + login, reopen browser.
I archive from the main bot list.

I have only tested on 1 bot, but I think the behavior is consistent.

4

Thanks — that detail (hedge combo, archived from the main list, only reappears after logout/reopen rather than a plain F5) was exactly what I needed, and it points straight at the cause.

You’ve found a real bug. Here’s what’s happening: when you archive a hedge-combo bot in v2, the archived state isn’t being persisted on the server — the request comes back “OK”, but the bot’s status never actually flips to archived. The dashboard hides it locally using a short-lived, per-session cache, which is why it stays hidden through an F5 but comes back the moment that cache is cleared (closing/reopening the browser or logging out).

So nothing is broken with your bot or your config — it’s a server-side persistence gap specific to archiving hedge-combo bots. I’ve logged it with the details for the team to fix. In the meantime, re-archiving works within a session, but it won’t stick across a full re-login until the fix ships. I’ll follow up here when it’s resolved.

5

Update: this is now fixed and live. :tada:

Here’s what was happening: archiving is only meant for stopped bots, but the dashboard was still letting you hit Archive on a bot that was still running. When you did, it showed a success message and hid the bot from your list — but since the bot wasn’t stopped, the archive never actually saved on our side. After a full reload (or logout/login) the bot came back, exactly as you described. Your hedge‑combo bot was still running, which is why it kept reappearing.

What’s changed:

  • If a bot is still running, the Archive option is now greyed out with a “Stop the bot first” note — so it’s clear up front instead of silently failing.
  • Once you stop the bot and then archive it, it now stays archived across reloads and re‑logins.

So on your end: stop the hedge‑combo bot first, then archive it — it’ll stick now.

Thanks for the report, and especially for noting it only came back after a re‑login rather than a plain refresh — that detail pointed straight at the cause. Let me know if you still see anything off.