From 6dd3a436f7edf228fa63663a99b9416712066bda Mon Sep 17 00:00:00 2001
From: Neel Shah <neel.shah@sentry.io>
Date: Tue, 10 Oct 2023 16:55:31 +0200
Subject: [PATCH] ref(crons): Remove outdated connect errors section (#8165)

---
 src/platforms/common/crons/index.mdx | 26 --------------------------
 1 file changed, 26 deletions(-)

diff --git a/src/platforms/common/crons/index.mdx b/src/platforms/common/crons/index.mdx
index 710a01a1b7219..babd39cfa21c2 100644
--- a/src/platforms/common/crons/index.mdx
+++ b/src/platforms/common/crons/index.mdx
@@ -261,32 +261,6 @@ GET /api/___PROJECT_ID___/cron/<monitor_slug>/___PUBLIC_KEY___/?status=error HTT
 Host: ___ORG_INGEST_DOMAIN___
 ```
 
-## Connecting Errors to Cron Monitors
-
-If you're capturing Sentry errors, you can link them to a Cron Monitor by using context.
-
-```python {tabTitle: Python}
-sentry_sdk.set_context("monitor", {
-    "slug": "<monitor_slug>",
-})
-```
-
-```php
-\Sentry\configureScope(function (\Sentry\State\Scope $scope): void {
-    $scope->setContext('monitor', [
-        'slug' => '<monitor_slug>',
-    ]);
-});
-```
-
-```javascript {tabTitle: JavaScript (Node.JS)}
-Sentry.setContext("monitor", {
-  slug: "<monitor_slug>",
-});
-```
-
-See [additional context examples](/platform-redirect/?next=/enriching-events/context/) for your platform.
-
 </PlatformSection>
 
 ## Alerts