deleted database still show up on page, why?

[William Mei]

a deleted database on a page still show up on that page, refresh the page does not fix it.

[Gabriela]

The database itself and the card that displays it on the page are two separate objects, and that's the whole reason for what you're seeing. When you delete the database it goes to the space Trash, but that action doesn't edit the page, so the page still holds the embedded database card. And while the database is only sitting in the Trash and hasn't been purged yet, that card can still resolve and render, so the page looks unchanged.

To get it off the page, open the page, go into edit mode, select the embedded database card and delete it, then Update. Deleting the database on its own won't ever remove that card for you, the page has to be edited.

If you want the database gone for good as well, purge it from Space settings > Content > Trash. A plain delete only soft-deletes it, which is part of why the card keeps showing.

Since a normal refresh didn't help, try a hard refresh (Cmd/Ctrl+Shift+R) or open the page in an incognito window or another browser too. A normal reload can serve a cached copy of the render, and that's quick to rule out before you start editing.

[Tomislav Tobijas]

Hey @William Mei ,

Can you maybe share what you're seeing/experiencing here? Are you saying that the database is displayed in content tree after it's been deleted, or did you embed the database to an existing page and after deletion it's still being displayed there? 🤔

I did try to replicate this with Live doc and an embedded database, but when I send database in track, the whole embed just disappears from the live doc.

Apart from what Gabriela said, it might be app database synchronization issue, but that usually resolves itself over time. 👀

Also, if you have other users on the site, can you check with them if they are seeing the same thing on their end?

Cheers,
Tobi

[William Mei]

Please see the screen capture as attached. 

the San Diego database was deleted and couldn't be searched(as highlighted in the picture), but it shows up under the page US Server Information always. I purged this database from Space settings>Content>Trash, still no luck, I go edit the page, cannot find the embedded database card as Gabriela mention below, no way to get rid of the San Diego highlighted.

[Gabriela]

Thanks for the screenshot, that changes the picture. What you're showing me is the San Diego entry hanging in the left content tree under US Server Information, which is a different beast from the embedded card I described, and that's why there was nothing for you to delete in edit mode. My earlier steps only apply when the database is embedded in the page body, so set that part aside for your case.

Since you've already purged it and it's gone from search, what you're left with is a stale tree entry. First thing I'd do is open that page in an incognito window, or have another user look, and check whether San Diego still hangs there. If it's gone for them, your own browser is holding a cached copy of the tree and clearing site data for Confluence will settle it. If everyone still sees it after the purge, the content is genuinely gone but the navigation hasn't caught up yet.

Also double-check the Trash is truly empty of it now, Space settings > Content > Trash, because a database can leave a separate reference behind and it's easy to purge one and miss the other.

If it's still there for every user a day after a clean purge, that's an index and tree desync on Atlassian's side, and Cloud gives you no manual reindex button to force it. That's the point where I'd raise it with Atlassian Support so they can rebuild the tree for the space. Can you check the incognito window and let me know? That tells us straight away which side of this we're on.

[William Mei]

it looks like the same thing. 

[Gabriela]

If that screenshot is the incognito window, then a cached copy in your browser is ruled out and the entry is genuinely stuck in the space tree on Atlassian's side.

The test that settles it fully is another person. Have a colleague open that same page and tell me whether San Diego still shows in the tree for them, since incognito still runs under your own account and a second user is what rules that out. While you're there, confirm the Trash is truly empty of it (Space settings > Content > Trash) and that there isn't a second San Diego reference under a slightly different name, because a database can leave one behind and it's easy to purge one and miss the other.

If another user still sees it a day after a clean purge, the content is gone but the tree hasn't caught up, and that's a reindex Atlassian has to run from their end — there's no button for it in Cloud. Databases are still in beta, so a leftover tree entry after a purge is the sort of thing to send to Support. Open a ticket with the space key, the database name, and a note that it persists after purge and in incognito, and they can rebuild the tree for the space.