Fetching and validating config file...
Successfully validated docs.json
Fetched all file paths
Fetched 3 OpenApi file(s):
  - access-management/scim/scimopenapi.json
  - console-api/capiopenapi.json
  - http-api/httpopenapi.json
Generated OpenAPI pages for navigation
Updating all paths...
Failed to parse page content at path client/Android.mdx: Unexpected closing tag `</CodeGroup>`, expected corresponding closing tag for `<Step>` (33:1-33:31)
Failed to parse page content at path client/Unity.mdx: Expected a closing tag for `<Step>` (32:1-32:34)
Failed to parse page content at path client/concepts/local-eval-adapter.mdx: Expected a closing tag for `<Tab>` (39:3-39:24)
Failed to parse page content at path client/concepts/persistent_assignment.mdx: Could not parse expression with acorn
Failed to parse page content at path client/javascript-sdk-stable-id.mdx: Expected a closing tag for `<Tab>` (36:3-36:27)
Failed to parse page content at path client/migration-guides/MigrationFromOldJsClient.mdx: Could not parse expression with acorn
Failed to parse page content at path experiments/implementation/getting-group.mdx: Could not parse expression with acorn
Failed to parse page content at path guides/first-feature.mdx: Expected a closing tag for `<Step>` (44:3-44:41)
Failed to parse page content at path infra-analytics/getting-started.mdx: Expected a closing tag for `<Tab>` (25:1-25:22)
Failed to parse page content at path integrations/azureai/embeddings.mdx: Expected a closing tag for `<Tab>` (17:3-17:23)
Failed to parse page content at path integrations/cloudflare.mdx: Unexpected closing tag `</Accordion>`, expected corresponding closing tag for `<Step>` (33:1-33:39)
Failed to parse page content at path integrations/data-connectors/segment.mdx: Could not parse expression with acorn
Failed to parse page content at path integrations/event_webhook.mdx: Could not parse expression with acorn
Failed to parse page content at path integrations/fastly.mdx: Expected a closing tag for `<Step>` (29:1-29:7)
Failed to parse page content at path integrations/vercel.mdx: Expected a closing tag for `<Step>` (42:3-42:9)
Failed to parse page content at path sdks/quickstart.mdx: Unexpected closing tag `</Tab>`, expected corresponding closing tag for `<Step>` (16:3-16:42)
Failed to parse page content at path sdks/user.mdx: Unexpected closing slash `/` in tag, expected an open tag first
Failed to parse page content at path server-core/migration-guides/java.mdx: Expected a closing tag for `<CodeGroup>` (19:1-19:12)
Failed to parse page content at path server/cpp.mdx: Expected a closing tag for `<Step>` (28:1-28:31)
Failed to parse page content at path server/go.mdx: Expected a closing tag for `<Step>` (31:1-31:31)
Failed to parse page content at path server/ruby.mdx: Could not parse import/exports with acorn
Failed to parse page content at path session-replay/cli-session-replay.mdx: Expected a closing tag for `<Tab>` (19:3-19:20)
Failed to parse page content at path session-replay/configure.mdx: Could not parse import/exports with acorn
Failed to parse page content at path session-replay/install.mdx: Unexpected closing slash `/` in tag, expected an open tag first
Failed to parse page content at path snippets/client/JavaScript/stableID.mdx: Expected a closing tag for `<Tab>` (19:1-19:25)
Failed to parse page content at path snippets/client/Next/proxying.mdx: Expected a closing tag for `<Tab>` (7:1-7:25)
Failed to parse page content at path snippets/client/React/installation.mdx: Unexpected closing slash `/` in tag, expected an open tag first
Failed to parse page content at path snippets/local-eval/android/_initialize.mdx: Expected a closing tag for `<CodeGroup>` (5:1-5:12)
Failed to parse page content at path snippets/local-eval/swift/_initialize.mdx: Expected a closing tag for `<CodeGroup>` (6:1-6:12)
Failed to parse page content at path snippets/server-core/java/installation.mdx: Expected a closing tag for `<version>` (115:40-115:49) before the end of `paragraph`
Failed to parse page content at path snippets/server-core/node/clientInitResponse.mdx: Unexpected closing slash `/` in tag, expected an open tag first
Failed to parse page content at path snippets/server-core/node/installation.mdx: Could not parse expression with acorn
Failed to parse page content at path snippets/server-core/python/clientInitResponse.mdx: Unexpected closing slash `/` in tag, expected an open tag first
Failed to parse page content at path snippets/server-core/python/initialization.mdx: Unexpected closing slash `/` in tag, expected an open tag first
Failed to parse page content at path snippets/server-core/rust/reference.mdx: Could not parse expression with acorn
Failed to parse page content at path snippets/server/java/_installBeta.mdx: Expected a closing tag for `<com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar>` (21:12-21:72) before the end of `paragraph`
Failed to parse page content at path snippets/server/java/_options.mdx: Expected a closing tag for `<ResponseField>` (14:1-14:69)
Failed to parse frontMatter content at path access-management/org-admin/experiment_policy.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 2, column 134:
     ... Set defaults for new experiments: While Statsig aims to provid
                                         ^
Failed to parse frontMatter content at path access-management/scim/okta_scim_team_management.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 3, column 153:
     ... hey also have two possible roles: `Admin` a
                                         ^
Failed to parse frontMatter content at path access-management/scim/okta_scim_troubleshooting.mdx: a line break is expected at line 3, column 16:
    description: | Error | Solution | |-------|---- ... 
                   ^
Failed to parse frontMatter content at path access-management/sso/google.mdx: end of the stream or a document separator is expected at line 2, column 14:
    description: - You will need to be the `Admin ... 
                 ^
Failed to parse frontMatter content at path access-management/sso/okta_sso.mdx: end of the stream or a document separator is expected at line 2, column 14:
    description: - You will need to be the `Admin ... 
                 ^
Failed to parse frontMatter content at path data-warehouse-ingestion/bigquery.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 6, column 71:
     ...  BigQuery, we need the following: - Granting Permissions to a St ... 
                                         ^
Failed to parse frontMatter content at path data-warehouse-ingestion/data_mapping.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 6, column 156:
     ... to be ingested into our platform:
                                         ^
Failed to parse frontMatter content at path docs/server-core/node/migration-guide/_statsig_options.mdx: a line break is expected at line 2, column 16:
    description: | Old Option                       ... 
                   ^
Failed to parse frontMatter content at path guides/open-source-script.mdx: can not read a block mapping entry; a multiline key may not be an implicit key at line 3, column 1:
    
    ^
Failed to parse frontMatter content at path integrations/data-connectors/mixpanel.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 6, column 93:
     ... on has two functions. - Incoming: Statsig can sync your Mixpanel ... 
                                         ^
Failed to parse frontMatter content at path integrations/datadog.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 2, column 69:
     ... cases to the Datadog integration: 1. [Config Changes](#config-ch ... 
                                         ^
Failed to parse frontMatter content at path messages/serverSDKConnection.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 138:
     ... est practice to implement either: 1. [bootstrapValues and
                                         ^
Failed to parse frontMatter content at path product-analytics/alerts-overview.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 3, column 70:
     ...  of alerts on the platform today: 1. **[Topline Metric Alerts](/ ... 
                                         ^
Failed to parse frontMatter content at path sdks/api-keys.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 2, column 52:
     ... are three main types of API keys: 1. **Client API Key**: Intende ... 
                                         ^
Failed to parse frontMatter content at path sdks/identify-users.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 2, column 126:
     ... now who the user is to determine:
                                         ^
Failed to parse frontMatter content at path session-replay/debug.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 3, column 59:
     ... e, you may encounter the warning: > "This session recording is t ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/connecting-your-warehouse/bigquery.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 83:
     ...  there are two supported methods: - Grant Permissions to a Stats ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/connecting-your-warehouse/clickhouse.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 70:
     ... khouse connector is in open Beta: some functionality may not be  ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/connecting-your-warehouse/databricks.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 81:
     ... cks, you will need the following: - Your Databricks Server Hostn ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/connecting-your-warehouse/trino.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 65:
     ...  Trino connector is in open Beta: some functionality may not be  ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/features/mex-on-warehouse-native.mdx: can not read a block mapping entry; a multiline key may not be an implicit key at line 8, column 1:
    
    ^
Failed to parse frontMatter content at path statsig-warehouse-native/features/use-case.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 71:
     ... riment results to new users only: A user is 'new' if they had ne ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/geotests/geotests-setup.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 3, column 105:
     ... using Statsig. The steps include: 1. Define your Geo Types 2. Co ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/geotests/introduction.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 98:
     ... er level. Some common causes are: - You don't have per-user cont ... 
                                         ^
Failed to parse frontMatter content at path statsig-warehouse-native/geotests/methodology.mdx: incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 7, column 67:
     ... relies on a few core assumptions: 1. You can reliably and random ... 
                                         ^
Failed to parse frontMatter content at path webanalytics/overview.mdx: can not read a block mapping entry; a multiline key may not be an implicit key at line 4, column 1:
    
    ^
Updated deployment with errors
Successfully saved config
Updating navigation...
Navigation updated