Collections Stuck in Archive

Hello, we noticed some weird behaviour with the archive where a question would say it's been archived but it was nowhere to be found.

Anyways, due to that I decided we would delete everything out of the archive as it was getting pretty big.

I selected everything in the archive at once and clicked "delete". Now, all the questions are gone but there are still 85 collections sitting there. Whenever I click delete the logs just give me:

Sep 13 00:17:55 metabase metabase[736]: 2023-09-13 00:17:55,825 DEBUG middleware.log :: #033[32mGET /api/search 200 259.0 ms (3 DB calls) App DB connections: 0/10 Jetty threads: 3/50 (6 idle, 0 queued) (53 total active threads) Queries in flight: 0 (0 queued)#033[0m
Sep 13 00:18:52 metabase metabase[736]: 2023-09-13 00:18:52,759 INFO middleware.exceptions :: Request canceled before finishing.

I am able to unarchive the collections.

[47b265b7-0a3c-470e-aba0-5158d6a7d4f9] 2023-09-12T18:15:20-06:00 INFO metabase.core 
Metabase v0.47.1 (bd278b9 release-x.47.x) 

Copyright © 2023 Metabase, Inc. 

Metabase Enterprise Edition extensions are NOT PRESENT.
[47b265b7-0a3c-470e-aba0-5158d6a7d4f9] 2023-09-12T18:15:20-06:00 INFO metabase.core Starting Metabase in STANDALONE mode
[47b265b7-0a3c-470e-aba0-5158d6a7d4f9] 2023-09-12T18:15:20-06:00 INFO metabase.server Launching Embedded Jetty Webserver with config: 
 {:port 3000}

[47b265b7-0a3c-470e-aba0-5158d6a7d4f9] 2023-09-12T18:15:20-06:00 INFO metabase.core Starting Metabase version v0.47.1 (bd278b9 release-x.47.x) ...
[47b265b7-0a3c-470e-aba0-5158d6a7d4f9] 2023-09-12T18:15:20-06:00 INFO metabase.core System info:
 {"file.encoding" "UTF-8",
 "" "OpenJDK Runtime Environment",
 "java.runtime.version" "11.0.18-ea+9-LTS",
 "java.vendor" "Red Hat, Inc.",
 "java.vendor.url" "",
 "java.version" "11.0.18-ea",
 "" "OpenJDK 64-Bit Server VM",
 "java.vm.version" "11.0.18-ea+9-LTS",
 "" "Linux",
 "os.version" "4.18.0-513.el8.x86_64",
 "user.language" "en",
 "user.timezone" "UTC"}

Delete them from the app db


If anyone else has this issue, just go

mysql> DELETE FROM collection WHERE archived = 1; 
Query OK, 84 rows affected (0.06 sec)