DIRECT ANSWER
Check whether the Scintilla report actually ran, whether that run produced a downloadable file, and whether the downloaded file opens. For recurring reports, compare the scheduled run, selected period, and data-as-of time. Preserve the error and test a smaller copy before changing the original report.
The report is due in the morning. Clicking download gives you nothing, an error, or a file you cannot open. Before rebuilding the report, establish where it stopped. A report that never ran needs a different investigation from a completed file sitting in your Downloads folder.
This guide covers Report Builder for U.S. first-party Walmart suppliers using Scintilla Basic or Charter. Use datasets and fields available to your account. It does not cover API, BI Link, Cloud Feeds, Marketplace reporting, or Sam’s Club. The checks below are Retail Reason’s diagnostic method, not a claim that every report has identical controls.
Where did the report stop?
Open the report record and copy its exact status and last-run information. Confirm the report name or identifier, dataset, selected dates, and file format. Check any current service or data-refresh notice. Then choose the branch that matches the evidence.
| What you can establish | Next useful check |
|---|---|
| You have a saved definition but cannot identify a run | Check whether a run was requested or scheduled. A saved recipe alone does not demonstrate execution. |
| A future run is scheduled | Compare its date, time, and displayed time zone with when you expected the file. |
| The run is processing or failed | Preserve the exact message and run time. Check the selected dataset, required settings, and any service notice. |
| A result is available but no file arrives | Inspect the browser’s download record for completion, cancellation, or a blocked transfer. |
| The file arrived but will not open | Record its extension, size, and the application’s exact error. Determine whether an archive must be extracted first. |
| The file opens but has old or unexpected data | Match the selected period and data-as-of information to this run. Download success does not establish freshness. |
Walmart’s public Report Builder overview describes building, customizing, previewing, scheduling, and sharing reports. It does not publish a universal export ceiling or processing deadline. Use current in-product guidance for the specific format and dataset instead of applying a limit remembered from another tool.
Could access or the report definition be the problem?
Confirm the supplier account and the report you intended to use. If a dataset, field, or shared report is unavailable, preserve the access message. Check the applicable entitlement before interpreting a missing control as a failed download. Our Basic and Charter comparison explains why account scope matters.
For a report you can edit, compare the current recipe with the last working version: dataset, columns, filters, time selection, and output format. A teammate’s report with the same name is not necessarily the same definition. Keep your original settings before making a test copy.
What does a smaller test actually tell you?
Use one completed period, a short explicit item list, and only the essential fields available in that dataset. Keep the metric definitions and other relevant filters consistent. Record what you reduced, and attempt the copy using the controls available to you.
If the small file works, increase one part of the scope at a time. That narrows the conditions associated with the failure. It does not prove the original exceeded a row limit; a field combination, period, transfer, or application problem may still need investigation.
If both versions fail, preserve both outcomes for support. Repeatedly submitting identical runs adds little evidence. If a file is already downloaded, test the local file problem before scheduling another extraction. Keep identifiers as text when importing data so leading zeros survive.
Why did the recurring report arrive with older data?
Record three separate times: the scheduled or actual run, the underlying data-as-of time where provided, and the download time. Also record the requested reporting period. A file downloaded today may be a previous result, or a new result built for an older date selection. If no data-as-of time is available, record it as unknown and check the dataset’s current refresh information. A missing transaction date alone does not prove a delayed refresh; the report may exclude that date or contain no activity for it.
Read the delivery option’s current description. Establish whether it follows a clock time or depends on a data update; do not assume every dataset offers both choices. Check the recurrence end date if one is shown. Missing email is also a separate observation from a missing report result.
For week-based work, confirm the actual boundaries with the Walmart week guide. If the file is usable and current and the comparison involves Boards or Channel Insights available to your account, move to the Boards and Channel Insights reconciliation guide.
A fictional run-and-file timeline
An analyst expects a complete Saturday-through-Friday week. These times and outcomes are invented, not Scintilla service expectations.
| Recorded time | Observation | What it establishes |
|---|---|---|
| 01:50 | The report record identifies a completed run. | A result exists for that run; its freshness still needs checking. |
| 01:53 | The browser records a completed file transfer. | The download stage finished. |
| 01:54 | The spreadsheet application reports that it cannot open the file. | The immediate failure is file opening, not evidence that the report never ran. |
| 02:02 | An approved file tool opens the result. The requested range ends Friday, but the available data is confirmed to cover only through Thursday. | File access is resolved. Friday’s coverage is still missing. |
The analyst reports those two conclusions separately and preserves the original file. Nobody marks the meeting data ready merely because the file opens.
What should go to support and your account team?
Open Scintilla Support in a browser with JavaScript enabled and sign in if prompted. Provide the report identifier, dataset, account context, exact error, timestamps and time zones, recipe, format, and small-test result. Specify whether generation, transfer, opening, or freshness remains unresolved. Use the account’s approved support channel for supplier data.
For recurring deadlines, Startup Success Lab’s buyer-calendar and answer-library guide helps assign the report owner, backup, readiness check, and next decision. This supports the team’s reporting process; platform errors still require the appropriate technical investigation.
Source review
Walmart’s public Report Builder description was checked September 13, 2026. Detailed in-product error handling and account entitlements were not independently verified for this article. The guide therefore uses observable evidence and makes no fixed claim about row limits, retention, processing times, or guaranteed delivery.