From 8e9443f54dd7c9cd5f308aa37ea4f277f3d35597 Mon Sep 17 00:00:00 2001 From: Jesse Rosenberger Date: Tue, 23 Apr 2024 16:53:13 +0300 Subject: [PATCH] docs(subscription-support): Try to fix formatting of L3 header. (#5004) --- docs/source/executing-operations/subscription-support.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/source/executing-operations/subscription-support.mdx b/docs/source/executing-operations/subscription-support.mdx index 2f2fe92d9c..8d22dafc44 100644 --- a/docs/source/executing-operations/subscription-support.mdx +++ b/docs/source/executing-operations/subscription-support.mdx @@ -173,6 +173,7 @@ If something crashes on your side for a specific subscription on specific events Also, when handling subscriptions with heartbeats disabled, make sure to store a subscription's request payload (including extensions data with callback URL and verifier) to be able to send the right events on the right callback URL when you start your lambda function triggered by an event. + ### Using a combination of modes If some of your subgraphs require [passthrough mode](#websocket-setup) and others require [callback mode](#http-callback-setup) for subscriptions, you can apply different modes to different subgraphs in your configuration: