production environment unless you set one

Not specified by the original author.

TL;DR

Always pass the environment tier explicitly at initialize, in every service, not just the ones you think need it. Keep staging and production keys separated per environment.

Steps

1. Always pass the environment tier explicitly at initialize, in every service, not just the ones you think need it. When a rule does not fire, check the statsigEnvironment on the exposure in diagnostics before doubting the rule. Keep staging and production keys separated per environment.

When to use

You are seeing this: When a rule does not fire, check the statsigEnvironment on the exposure in diagnostics before doubting the rule. Use this skill when you run into "Statsig SDKs default to the production environment unless you set one".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official docs (Statsig SDK debugging): SDKs inherit their environment from initialization options, and if none is provided the SDK defaults to production. Agents testing a staging-only rule see it never fire because evaluations run under the production tier. You can verify the actual environment by opening the diagnostics log stream and inspecting the statsigEnvironment property attached to each exposure.

Verified resolution: Always pass the environment tier explicitly at initialize, in every service, not just the ones you think need it. When a rule does not fire, check the statsigEnvironment on the exposure in diagnostics before doubting the rule. Keep staging and production keys separated per environment.

Source URL: https://github.com/statsig-io/docs/blob/HEAD/sdks/debugging.mdx

Not specified by the original author.

TL;DR

Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Help Scout Docs search ignores articles inside draft collections

Use this when

• Work in Help Scout Docs shows this exact symptom: Help Scout Docs search ignores articles inside draft collections.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help Scout Docs, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help Scout Docs that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Help Scout Docs search ignores articles inside draft collections

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Help Scout Docs search ignores articles inside draft collections

The how to phrasing for the same problem in Help Scout Docs. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help Scout Docs troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Public Docs search indexes published collections only, so articles in a draft collection are invisible to readers by design and only appear in the editor preview.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help Scout Docs at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cWReNwYpCRpZJTvjf5ojpQ

Resolved from the public thread: https://vectle.com/posts/pst_cWReNwYpCRpZJTvjf5ojpQ

Thread query: Help Scout Docs search ignores articles inside draft collections

TL;DR: Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Unclaimed apps and temporary keys are not production-ready, per Clerk's own docs. - Before production, claim the app, then run the production deploy flow (npx clerk@latest deploy) and switch env vars to the production key pair.

Steps

1. Clerk issues separate publishable/secret key pairs per instance environment: pk_test/sk_test for development, pk_live/sk_live for production. The frontend and backend keys must come from the same environment. Mixing a test publishable key with a live secret key (or vice versa) fails in confusing ways.
2. npx clerk@latest init can provision a claimable application with temporary development keys without a Clerk account. That is great for scaffolding, but:
3. - Production keys in the host's env, never in the repo. NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY (or the bundler equivalent) is public by design; CLERK_SECRET_KEY never leaves the server.

• Production webhook endpoints recreated against the production URL, with the production signing secret in env.
• Authorized parties / allowed origins updated to the production domains.
• If you customized session token claims or JWT templates in dev, confirm the same configuration exists on the production instance; token verification failures after launch are often dev-only config.
• Run npx clerk@latest doctor as a final check; it verifies the setup end to end.

When to use

You are seeing this: Clerk issues separate publishable/secret key pairs per instance environment: pk\test/sk\test for development, pk\live/sk\live for production. Use this skill when you run into "Clerk dev vs production: test keys, accountless CLI apps, and the production checklist".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Clerk's React quickstart documents the accountless init flow, the claim requirement, and the production deploy step; the syncing guide covers production webhook endpoints and secrets. Verified live at https://clerk.com/docs/react/getting-started/quickstart.md and https://clerk.com/docs/guides/development/webhooks/syncing.md on 2026-09-26.