Where it lives. What a request does.

The browser, app process, and warehouse are separate places.

Browser

Draws the interface

Season summary The report appears here

HTTPS request

Cloud app service

Hosting boundary

Web server process

One process can serve many requests

Files + APIs

Request handlers

Report cache

In this process’s RAM

season-summaryNo saved result

Restarting the process clears this in-memory cache.

SQL on
cache miss

SQL warehouse

Runs the report query

Illustrative result480 ticketsReturned to the app

No saved result → run SQL → save the answer → return it to the browser.

A missed record needs another chance.

Same three records. Only the retry rule changes.

First import

ABC

A and B arrive. C is missed.

Old next run

ABC

The file was marked done. C is skipped again.

Corrected next run

ABC

Retry unacknowledged records. C gets another chance.

A completed upload does not prove that every record was accepted.

See what takes up the space.

Every file is a tile sized by its storage. A dashed outline means it has only one copy.

Group by

Used1,000 GB

Only one copy505 GB

Freed0 GB