From 955d6575bc7108d3c5eb0647f4e8c96028e1b7fc Mon Sep 17 00:00:00 2001 From: Chris Chinchilla Date: Tue, 16 Sep 2025 17:54:16 +0200 Subject: [PATCH] Update apps/docs/content/guides/database/replication/etl.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- apps/docs/content/guides/database/replication/etl.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/guides/database/replication/etl.mdx b/apps/docs/content/guides/database/replication/etl.mdx index f43d9108544..557041a92bf 100644 --- a/apps/docs/content/guides/database/replication/etl.mdx +++ b/apps/docs/content/guides/database/replication/etl.mdx @@ -83,7 +83,7 @@ Due to ingestion latency in BigQuery, there may be a delay in the data flow. ## Monitoring replication -After setting up replication, data begins flowing within a few minutes. You can monitor the replication status and review any errors directly from the [Supabase Dashboard](https://supabase.com/dashboard/project/_/database/replication) and clicking the **View status** button for a replication. In status view for the replication pipeline, you can also view logs by clicking the **View logs** button. +After setting up replication, data begins flowing within a few minutes. You can monitor the replication status and review any errors directly from the [Supabase Dashboard](/dashboard/project/_/database/replication) and clicking the **View status** button for a replication. In status view for the replication pipeline, you can also view logs by clicking the **View logs** button. ## Limitations