Skip to content

Commit e8a4c90

Browse files
authored
Remove recovery requests (#1608)
1 parent 55f19cc commit e8a4c90

File tree

1 file changed

+1
-3
lines changed
  • docs/monitoring/recovering-failed-events

1 file changed

+1
-3
lines changed

docs/monitoring/recovering-failed-events/index.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Recover failed events"
33
sidebar_position: 4
44
sidebar_label: "Recover failed events"
5-
description: "Fix and reprocess failed events using SQL recovery, manual recovery from buckets, or Console data recovery requests."
5+
description: "Fix and reprocess failed events using SQL recovery or manual recovery from buckets."
66
keywords: ["event recovery", "failed event recovery", "reprocess failed events"]
77
---
88

@@ -13,5 +13,3 @@ A typical recovery process runs a script over a set of failed events to solve th
1313
The best way to recover failed events is to [set up loading failed events into a separate table in your warehouse or lake](/docs/monitoring/exploring-failed-events/index.md). [Use SQL to recover](/docs/monitoring/recovering-failed-events/recover-with-sql/index.md) the events.
1414

1515
If you don't have a Failed Events Loader, you can [manually recover](/docs/monitoring/recovering-failed-events/manual/index.md) failed events from their S3 or GCS buckets.
16-
17-
Finally, you can also use Snowplow Console to [submit a data recovery request](https://console.snowplowanalytics.com/recovery) to our Support team.

0 commit comments

Comments
 (0)