Fix quotation downloads that fail or never arrive
Work out why a quotation CSV, PDF or XLSX export refuses to download, shows success without a file, or never arrives after being queued.
Quotation CSVs and PDFs are produced inside the app's in-browser filesystem and handed to the browser as a normal download, followed by a 'Successfully downloaded files' toast. If the generated file exists but is empty, the app refuses with the error toast 'Cannot download empty content' — usual causes are an empty quotation table (nothing priced under the current scope/filters) or generation that aborted midway; regenerate the quotation and retry. Two follow-on gotchas: (1) after a successful download the temporary file is deleted from the in-app filesystem and the blob URL is revoked immediately, so using the browser's own 'retry download' on that entry will fail — the export must be re-triggered from inside the app; (2) downloads are fired via a simulated link click, so aggressive browser download-blocking settings can swallow the file while the app still shows success; have the client check the browser's download permissions for the site. For XLSX exports the filename is pricing_quotation.xlsx, or an auto-generated output-<timestamp>-<random>.xlsx when no name is supplied by the engine.
When an XLSX quotation download fails, the CSV and PDF quotation exports are separate in-browser actions and can still be downloaded.
CSV output omits images, so it is not a substitute when pictures are required.
✓ ଅକ୍ଟୋବର 19, 2026 ରେ ପ୍ରଡକ୍ଟରେ ଯାଞ୍ଚ କରାଯାଇଛିEvery quotation/production export first runs pre-output checks plus a violations pass (loader shows 'Checking for violations...'). Panel-subset outputs are an exception: they skip the violations pass and are handed off to be processed on the backend, so no violations toast appears for them. Admin preferences can block the download, each with its own error toast that clients frequently miss: (1) Enforce active sales channel — if enabled and the design has no active sales channel selected: 'Downloading output for design without active sales channel preference is not permitted'; (2) No outputs for unapproved designs — blocks order-booking/ERP/purchase-order class outputs on unapproved designs; (3) No outputs for unlocked designs — same for unlocked designs; (4) No Outputs For Designs With Violations And Issues — if catalogue-constraint violations exist, a sticky toast asks to resolve all violations or turn the preference off. Quotation exports (the quotation download and the CSV/XLSX quotation exports) are exempt from the approval and lock preferences: only the active-sales-channel and violations preferences can block them. A design can be individually exempted from the violations block (info toast: 'Design Exempted from blocking output due to violations'). Marketplace/seller users bypass all these gates, and the approval/lock gates do not apply to MES users. Triage script: ask which toast flashed; if none was seen, reproduce with the client and watch the top of the screen, then check admin preferences and the violations panel for that design.
Server-generated outputs (presentation sheet PDFs, CAM/saw outputs, engine-generated design outputs) are queued on the backend. The app posts the job, shows a persistent 'Generating your output' toast whose detail reads 'Added to the download queue' (and, while waiting, a queue position or 'Processing…'), then polls job status every 5 seconds from that browser tab. On completion it shows 'Your output is ready' and auto-triggers the file download; on failure a sticky 'Your output could not be generated. Please try again later.' appears. Silent rules that explain most tickets: (1) the poller lives only in that tab — if the user refreshes, navigates away, or closes the tab, the job still completes on the server but nothing will ever download; they must re-trigger the export; (2) there is no timeout on the poller, so a job stuck in the queue leaves the 'Generating your output' toast (detail 'Added to the download queue' or a queue position) up indefinitely — that toast staying for many minutes means the queue is backed up or the job silently died, and it is worth checking the output queue on the backend; (3) if the status check itself errors, polling stops with 'Something went wrong with output generation. Please try again later'. The auto-download briefly suppresses the browser's leave-site warning; that is intentional.