Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-06

Recover deleted or overwritten data (7-day time travel)

How to see and recover a datalake table as it was at a moment in the last 7 days, from the Data console, and what the screen cannot do yet.

On this page (4)

Every table in your datalake (Bronze, Silver and Gold) keeps the state of the last 7 days. If a load deleted rows, a transformation overwrote the table with the wrong result or someone removed data by mistake, you can see the table as it was at a moment in those 7 days and copy that state back.

What is guaranteed

The window is 7 days (168 hours) in every layer, and it also holds when the table was recreated by a full load or by a Silver processed again. After 7 days the old state can no longer be read.

1. See the table as it was#

In Data › Console, write the query with FOR SYSTEM_TIME AS OF and the moment you want (in UTC — Brasília is UTC−3):

sql
SELECT *
FROM `yourprefix_silver.clientes`
  FOR SYSTEM_TIME AS OF TIMESTAMP '2026-10-06 15:38:30+00'
LIMIT 100

Use Estimate first: the query reads the table at that moment and is billed like any other. To find the right moment, check in Runs when the load that broke the table ran and pick a moment before it.

2. Copy the old state into a new table#

In the same console, save the old state into a table with another name and check it before changing anything:

sql
CREATE TABLE `yourprefix_silver.clientes_recovered` AS
SELECT *
FROM `yourprefix_silver.clientes`
  FOR SYSTEM_TIME AS OF TIMESTAMP '2026-10-06 15:38:30+00'

After checking, decide calmly: point the dashboard at the recovered table, or fix the cause in the pipeline and process again. Do not overwrite the original table before checking — overwriting is exactly what you want to undo.

What the screen cannot do yet#

  • There is no Restore version button and no list of table versions: recovery is through the console, as above. If you prefer, open a ticket (or ask Aiô) and the team does it for you.
  • The 7-day window is not configurable per workspace.
  • The retention of run logs follows the Data Retention Policy; it does not change the window above.

Real example#

In the integration test of 06/10/2026, two Silver transformations with the same name in different pipelines wrote to the same table, and the second erased the first (today the product refuses the repeated name). The erased version was read with the query in step 1, for the moment before the second processing: 200 rows, all with the calculated column the second version had lost.

Related links