[bug]: <short summary>Latency and 500 Errors during CLI Multipart Uploads (Testnet)

[GENESIS-SOARES17]

Affected product

SDK (JS/TS)

Version / Commit / Build

S: Linux Mint / Fedora (Aspire F5-573G)

Platform / Environment

Linux

Steps to Reproduce

2. Environment (Ambiente):

OS: Linux Mint / Fedora (Aspire F5-573G)

Network: Aptos Testnet (https://api.testnet.aptoslabs.com/v1)

Tool: Shelby CLI (Node.js v24.15.0)

3. Specific Items to Report (Itens Específicos):

Item A: Sync Delay (Atraso de Sincronia)

Explanation: Files marked as "Success" in the CLI take more than 10 minutes to populate the "All Resources" tab.

Evidence: Usage dashboard shows 0 MiB even after multiple successful transfers (See attached screenshot image_97931d.png).

Item B: Server Error 500 (Erro Interno)

Explanation: Intermittent Failed to complete multipart upload! status: 500 errors. This suggests the indexer or the storage provider is not handling concurrent requests well.

Item C: Mandatory Parameters (Expiração Obrigatória)

Explanation: The CLI requires --expiration and a destination name, but the documentation/help command does not always make this clear for beginners.

4. Expected Behavior (O que deveria acontecer):

"The Shelby Explorer should reflect the uploaded 'Blobs' immediately after a successful CLI confirmation, and the web interface 'Upload' button should remain active for selected files."

Expected Behavior

"The Shelby Explorer should reflect the uploaded 'Blobs' immediately after a successful CLI confirmation, and the web interface 'Upload' button should remain active for selected files

Actual Behavior & Errors

🚀 Upload Summary
────────────────────────────────────────────
📦 File: ARQUIVOS PARA ENVIAR/ENV111.PNG
📁 Blob Name: ENV111.PNG

🧮 Filelist created (1 entry)
Continue? Yes

🕒 Expires: Dec 31, 2026, 9:00:00 PM
✖ An unknown error occurred : Failed to complete multipart upload! status: 500, body: {"error":"Internal Server Error"}

Logs / Screenshots

Contact (Optional)

No response

Pre-Checks

• I've searched existing issues
• This is not a security vulnerability (see SECURITY.md)