From b0c39a805efe6503e526a57231bcbaef157114be Mon Sep 17 00:00:00 2001 From: typedarray <90073088+0xOlias@users.noreply.github.com> Date: Thu, 29 Feb 2024 16:21:41 -0500 Subject: [PATCH] docs: fix (#674) Co-authored-by: o-az --- docs/pages/docs/guides/production.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/docs/guides/production.mdx b/docs/pages/docs/guides/production.mdx index c1e7a0595..37f7d2f4a 100644 --- a/docs/pages/docs/guides/production.mdx +++ b/docs/pages/docs/guides/production.mdx @@ -46,7 +46,7 @@ After a moment, your Ponder service should redeploy successfully. Check the **Bu ### Zero-downtime deployments -Ponder supports zero-downtime deployments by waiting until all events have been processed before responding as healthy. To support long-running backfills, Ponder apps will begin responding as healthy _before_ the backfill is complete if it exceeds the `maxHealthcheckDuration`. This option defaults 240 seconds (4 minutes), and is configurable using [`options.maxHealthcheckDuration`](/api-reference/ponder-config#options). +Ponder supports zero-downtime deployments by waiting until all events have been processed before responding as healthy. To support long-running backfills, Ponder apps will begin responding as healthy _before_ the backfill is complete if it exceeds the `maxHealthcheckDuration`. This option defaults 240 seconds (4 minutes), and is configurable using [`options.maxHealthcheckDuration`](/api-reference/config#options). If you're using Railway, Ponder will set `maxHealthcheckDuration` automatically according to the **Healthcheck Timeout** specified in your app service settings.