fal Release Notes
Last updated: Mar 12, 2026
- Mar 11, 2026
- Date parsed from source:Mar 11, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Interval Selection and Chart Zoom in Analytics
fal highlights a new Interval picker in App Analytics letting users bucket metrics from 30 seconds to 1 month. It adds click and drag chart zoom for quick incident isolation and comparative analysis across Requests, Runners, and Error Analytics tabs.
Interval picker
The analytics pages now include an Interval picker that lets you control how metrics are bucketed — choose from 30 seconds, 1 minute, 5 minutes, 10 minutes, 1 hour, 1 day, 1 week, or 1 month depending on your selected date range
Use finer intervals (30 sec, 1 min) to pinpoint exact moments when latency spiked or error rates changed, and wider intervals (1 day, 1 week) for high-level trends over longer periods
Click and drag on any chart in App Analytics to select a time range and instantly zoom into that window — the date range updates automatically so you can isolate an incident, compare before-and-after a deployment, or drill into a traffic spike without manually adjusting date pickers
The Interval picker is available on both the Requests and Runners tabs in App Analytics, as well as in Error Analytics
Original source Report a problem - Mar 11, 2026
- Date parsed from source:Mar 11, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header App List View
fal unveils a new compact list view toggle on the app listing page, showing performance columns and saving the preferred layout.
App List View
Toggle between card view and a new compact list view on the app listing page using the view switcher in the toolbar.
List view displays your apps as rows with columns for type, runners, requests/min, latency, errors, machine type, and last updated — making it easy to scan and compare performance across many apps at once.
Your view preference is saved automatically, so you’ll see the same layout next time you visit.
Especially useful for teams managing dozens of serverless apps who need to quickly spot which apps need attention.
Original source Report a problem All of your release notes in one feed
Join Releasebot and get updates from fal and hundreds of other software products.
- Mar 11, 2026
- Date parsed from source:Mar 11, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Error Types in API Responses
fal introduces a machine readable error_type field in API responses that classifies failures like request_timeout and runner_server_error. this enables smarter retry logic and clearer error monitoring. developers can distinguish transient issues from client errors to optimize retries and observability.
Error Types in API Responses
Error responses now include a machine-readable error_type field identifying the specific failure category — such as request_timeout, runner_disconnected, runner_scheduling_failure, or runner_server_error
Use error_type to build smarter retry logic: runner and timeout errors (e.g. runner_connection_timeout, startup_timeout ) are typically transient and worth retrying, while client errors like bad_request should not be.
Track error_type values in your monitoring to spot trends — for example, frequent runner_scheduling_failure errors may indicate you need to increase max_concurrency
See Error Reference — Request Error Types for the full list of error types, status codes, and handling guidance.
Original source Report a problem - Mar 11, 2026
- Date parsed from source:Mar 11, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Termination Grace Period
fal introduces termination_grace_period_seconds to tune in-flight shutdown time with a default of 5s and a max of 30s.
Termination Grace Period
New
termination_grace_period_seconds parameter lets you control how long a runner has to finish in-flight requests and run teardown() before being forcefully killed
Defaults to 5 seconds, configurable up to a maximum of 30 seconds
See Scale Your Application — Termination Grace Period for the full shutdown lifecycle and best practices.
Original source Report a problem - Mar 11, 2026
- Date parsed from source:Mar 11, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Termination Grace Period
fal introduces termination_grace_period_seconds to control shutdown timing for runners with a default of 5 seconds and a max of 30 seconds, guiding safe teardown practices.
Termination Grace Period
New termination_grace_period_seconds parameter lets you control how long a runner has to finish in-flight requests and run teardown() before being forcefully killed
Defaults to 5 seconds, configurable up to a maximum of 30 seconds
See Scale Your Application for the full shutdown lifecycle and best practices.
Original source Report a problem - Feb 25, 2026
- Date parsed from source:Feb 25, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header App Tagging
fal enables in-dashboard custom tagging to organize, filter, and manage serverless apps by team or label
App Tagging
You can now create and assign custom tags to your serverless apps directly from the dashboard
Organize your app listing by tagging apps by team, project, model type, or any label that makes sense for your workflow
Filter by tag in the app list to quickly find the apps you need
Create, assign, and remove tags right from the app listing page — no CLI or API needed
Tags are visual labels for organizing your dashboard — they don’t affect app behavior, routing, or secrets. For isolated deployment stages (dev, staging, production), use Environments instead.
Original source Report a problem - Feb 25, 2026
- Date parsed from source:Feb 25, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header App Tagging
fal unveils tagging for serverless apps in the dashboard to create assign and filter by tags for easier organization using Environments for dev, staging and production.
App Tagging
You can now create and assign custom tags to your serverless apps directly from the dashboard
Organize your app listing by tagging apps by team, project, model type, or any label that makes sense for your workflow
Filter by tag in the app list to quickly find the apps you need
Create, assign, and remove tags right from the app listing page — no CLI or API needed
Tags are visual labels for organizing your dashboard — they don’t affect app behavior, routing, or secrets. For isolated deployment stages (dev, staging, production), use Environments instead.
Original source Report a problem - Feb 23, 2026
- Date parsed from source:Feb 23, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Machine Type in Runner Output
fal announces that Runner output now shows machine type for each runner and JSON output includes machine_type field.
Machine Type in Runner Output
fal runners list and fal app runners now display the machine type for each runner (e.g. GPU-A100, GPU-H100).
JSON output (--output json) also includes the machine_type field for each runner.
Original source Report a problem - Feb 23, 2026
- Date parsed from source:Feb 23, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Machine Type in Runner Output
fal adds machine type display to runner output, showing GPU types like GPU-A100 and GPU-H100.
Machine Type in Runner Output
fal runners list and fal app runners now display the machine type for each runner (e.g. GPU-A100, GPU-H100)
JSON output (--output json) also includes the machine_type field for each runner
Original source Report a problem - Feb 17, 2026
- Date parsed from source:Feb 17, 2026
- First seen by Releasebot:Mar 12, 2026
Navigate to header Runner FAILURE_DELAY Status
fal introduces FAILURE_DELAY status for runners in cooldown after setup failure and adds filter capability with fal runners list --state failure_delay.
Runner
FAILURE_DELAY
StatusRunners that fail during setup() now show a FAILURE_DELAY status, making it easier to identify runners that are in a cooldown period before retrying initialization
You can filter runners by this state using fal runners list --state failure_delay
See Understanding Runners for details
Original source Report a problem