unclecode / unclecode/crawl4ai-cloud-sdk

Storage usage is not fully cleaned after “Clear All”, and UI does not refresh updated storage size automatically

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Page: /storage
Plan: free
Browser: Chrome/147.0.0.0 Safari/537.36
Time: 2026-05-07T16:55:49.449Z


Describe the issue:

Description

When triggering Clear All or deleting multiple stored items, the storage cleanup does not appear to fully update in the UI after the job completes.

For example, I opened the portal and the storage usage showed around 300MB. Then I deleted around 100 items, which should have freed roughly 100MB. After the deletion job completed successfully, the UI still showed 300MB used storage.

The storage value only updated correctly after I manually refreshed the page.

Expected Behavior

After the Clear All or delete job finishes:

  • The deleted storage should be fully cleaned up.
  • The storage usage value should be recalculated.
  • The UI should automatically refresh and show the new storage amount without requiring a manual page refresh.

Actual Behavior

After the cleanup/delete job completes:

  • The UI still shows the old storage value.
  • In my case, it continued showing 300MB even after deleting roughly 100MB worth of items.
  • The correct value only appeared after manually refreshing the browser page.

Steps to Reproduce

  1. Open the portal.
  2. Check the current storage usage.
    • Example: 300MB
  3. Delete multiple stored items or trigger Clear All.
  4. Wait until the delete/cleanup job finishes.
  5. Check the storage usage shown in the UI.
  6. Notice that the UI still shows the old value.
  7. Refresh the page manually.
  8. The updated storage value appears.

Impact

This makes users think the cleanup did not work, or that storage is still being consumed even after deleting items.

It also creates confusion because the backend job may have completed, but the UI does not reflect the new state until a manual refresh.

Suggested Fix

After the delete or clear-all job completes, the frontend should re-fetch the storage usage and update the UI state automatically.

The backend should also confirm that all related storage records/files are actually removed and that the reported usage is recalculated correctly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the /storage page and trace the Clear All and multi-delete completion flow, including the storage usage request. Check both the cleanup result and the UI refresh after the job finishes. Done means deleted storage is reflected in the recalculated value without a manual page refresh.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.