Browser errors and limits
Diagnose model downloads, runtime compatibility, unsupported inputs, and cancellation.
Download and integrity failures
The first run needs network access for the selected model (34.8–85.1 MB) and browser runtime. If a download is interrupted, retry on a reliable connection. A size or checksum mismatch fails explicitly; clear the model cache and retry. The application does not send the forecast to a server when the browser download fails.
Model and device limits
The browser models use a fixed 512-point context, with up to 64 future steps for Chronos-Bolt and 32 for Timestral. Timestral weights are under Mistral's modified MIT license, which excludes companies above $20M in monthly revenue. Memory consumption exceeds the weight-file size because the runtime also allocates tensors and graph state. Some devices or browser configurations may not support the required worker and WASM features. Unsupported model IDs and input shapes are errors rather than proxy forecasts.
Cancel and recover
Cancel forecast aborts the active request by terminating its worker. Start another run after correcting the input or device issue. Cache clearing removes downloaded weights, not your saved input library. If the browser cannot run the model, inspect its directory page for external deployment options instead of assuming an automatic fallback.