August 7, 2026

Preserve quarantine data across compatible deployments

Forward now retains the existing quarantine table when a Data Source deployment changes its sorting key, partition key, or column types without changing the set of columns.

Quarantined rows remain available to users after the deployment instead of requiring support help to recover them.

The Organization Workspaces table now shows seven-day sparklines for vCPU time, memory, and errors. Totals remain available if a trend query times out.

Improvements and bug fixes

  • [Forward]: ALTER-based deployments can now drop a column across a landing Data Source and Materialized View flow. The Materialized View query is updated before the referenced column is removed.
  • [Forward]: DynamoDB-backed Data Sources now show the correct type and detail link in the UI.
  • [All]: Invalid UTF-8 ingestion now returns a clear HTTP 400 error instead of an internal failure.
  • [Forward]: Classic to Forward migrations no longer fail when a legacy Data Source lacks cached engine metadata.
  • [All]: Copy job timeout and memory errors now point to on-demand compute when it is applicable.
  • [Classic]: The region list in the workspace menu no longer reorders while workspace information loads.
  • [All]: Delete, Copy, and Sink job concurrency errors now clarify that working and queued jobs both count toward the limit.

From the blog

Better organization-wide visibility, for every Tinybird user: A tour of the new Organization Overview and Logs pages available to organization members.

Slate scopes product ideas around users, not infrastructure: How Slate replaced a Redis bottleneck with Tinybird to deliver real-time prices and profit and loss data.

From OLTP to OLAP: 7 ClickHouse® Optimization Mistakes: Seven common OLAP modeling and query mistakes, with practical fixes.