Accessing Database via Console

Hi everyone, I am running a self-hosted Appwrite v1.9.0 instance. When I click on one particular database in the Console, a loading indicator appears at the top of the page, but the database view never opens.

The rest of the Console remains visible, but it seems unable to finish loading that database. Has anyone else experienced this or found a solution?

Hey, I can help with this. Usually when one specific database hangs like that in Appwrite it's either a large collection/attribute count causing the console API call to time out, or a corrupted/orphaned collection reference in that database that the console can't resolve when it tries to fetch metadata. Sometimes it's also a permissions issue where a collection inside has broken document security rules.
Can you check your browser console or network tab when you click into that database and see if any API call is failing or just hanging (like a 500 or a pending request that never resolves)?

Thanks, @Albert Cameron . I checked the browser console, network requests, and the downloaded HAR file from network requests.

All API requests were completing successfully with HTTP 200 responses, and the list responses contained the expected total values. The issue turned out to be a Console UI naming collision in one table.

That table had a custom column named actions. The Appwrite Console also injects its own internal spreadsheet column named actions. When Svelte rendered the column list, both entries used the same key, which triggered the each_key_duplicate error and prevented the database view from loading. The later Cannot read properties of undefined (reading 'total') errors were secondary errors after the initial component crash.

I renamed the custom column from actions to actionItems using the update-column API with the newKey parameter. After verifying the metadata and hard-refreshing the Console, the database opened normally.

So the database itself was healthy. The issue was caused by the Console rendering a user-defined actions column alongside its own internal actions column.

This was the console error messages before i made the fix:

CmVFoSLP.js:1
Uncaught Error: https://svelte.dev/e/each_key_duplicate
    at Se (CmVFoSLP.js:1:1933)
    at CmVFoSLP.js:2:5189
    at Zr (CmVFoSLP.js:1:27430)
    at ei (CmVFoSLP.js:1:28480)
    at B (CmVFoSLP.js:1:23332)
    at Cr (CmVFoSLP.js:1:24674)
    at aa (CmVFoSLP.js:2:4760)
    at header (V7AL4vJL.js:268:3980)
    at fa (CmVFoSLP.js:2:8256)
    at children (CdnGxCB0.js:36:26407)

96.Ju9Pcisb.js:1
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'total')
    at 96.Ju9Pcisb.js:1:11017
    at Zr (CmVFoSLP.js:1:27430)
    at Sn (CmVFoSLP.js:1:17285)
    at Cn (CmVFoSLP.js:1:17340)
    at Yr (CmVFoSLP.js:1:26999)
    at Yr (CmVFoSLP.js:1:26992)
    at Z (CmVFoSLP.js:1:29159)
    at CmVFoSLP.js:3:11097
    at HTMLSpanElement.S (CdnGxCB0.js:4:63433)
    at CmVFoSLP.js:1:31744

CmVFoSLP.js:1 
Uncaught TypeError: Cannot read properties of undefined (reading 'total')
    at 96.Ju9Pcisb.js:1:11017
    at Zr (CmVFoSLP.js:1:27430)
    at Sn (CmVFoSLP.js:1:17285)
    at Cn (CmVFoSLP.js:1:17340)
    at Z (CmVFoSLP.js:1:29181)
    at 96.Ju9Pcisb.js:1:11536
    at Zr (CmVFoSLP.js:1:27430)
    at Sn (CmVFoSLP.js:1:17285)
    at Cn (CmVFoSLP.js:1:17340)
    at Z (CmVFoSLP.js:1:29181)

Thanks for sharing the root cause that was a really nice catch. The actions column collision isn't something I'd have expected, so I learned something new from your findings. If you run into any other Appwrite issues or need help debugging similar edge cases, feel free to reach out. I'd be happy to help and can also take on troubleshooting work if you ever need an extra hand.