Update from code changes: document screenshot readiness timeout env var#979
Merged
Conversation
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
pimmey
approved these changes
Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new
HEADLESS_BROWSER_SCREENSHOT_TIMEOUT_MSenv var that makes the previously hardcoded 180s screenshot readiness timeout configurable.Changes
HEADLESS_BROWSER_SCREENSHOT_TIMEOUT_MSrow (default180000) to the headless browser environment variables table inself-host/customize-deployment/environment-variables.mdx.TIMEOUT) must be ≥ this value, otherwise it becomes the binding limit.Context
Source PR: lightdash/lightdash#25399 —
feat(backend): make screenshot readiness timeout configurable.