Modal billing report exited successfully but returned only two resource rows from the preceding hour

With Modal Python/CLI 1.5.5, I was collecting per-application CPU, memory and GPU costs after completed jobs. During the current UTC hour, modal billing report --start 2026-09-08 --resolution h --show-resources --json exited successfully but returned only two resource rows from the preceding hour, even though modal billing summary --json already showed deployed GPU usage. A previously saved export contained later-hour rows, so the newer report appeared to have lost billing data. Comparing the workspace summary with the application report did not resolve the discrepancy because they also have different attribution scopes. There was no error or warning about the missing current-hour costs.

In the observed Modal 1.5.5 CLI, the default exclusive --end is now, while --resolution h reports full requested hour intervals. The still-open current-hour bucket is therefore excluded by a default-end query, even when some usage within that hour has already been recorded. This is not evidence that the jobs were free or that earlier charges were removed.

For an as-of-now view that includes already-recorded usage in the current hour, provide an exclusive end covering that whole bucket. The following pair was exercised while the UTC date was 2026-09-08 (substitute the appropriate calendar dates):

# Default end=now: only the preceding hour appeared in this run.
modal billing report --start 2026-09-08 --resolution h --show-resources --json

# Explicit next-day UTC end: includes the current hour's recorded usage.
modal billing report --start 2026-09-08 --end 2026-09-09 --resolution h --show-resources --json

The first command returned 2 CPU/memory rows from 18:00 UTC. The second returned 7 rows across 18:00 and 19:00 UTC, including the recorded H100 usage. modal billing report --help documents the exclusive end, its default of now, and full-interval reporting; the important interaction is that a later invocation can return fewer rows than an earlier export if their end bounds differ.

An explicit future bucket boundary does not make an invoice final or eliminate provider reporting lag. Preserve the query range and observation time, and do not release unresolved spending reservations merely because a row is absent. Also keep workspace-wide billing summary separate from application-attributed costs; it includes unrelated applications and storage.