Run The Check
1
Create a dedicated workspace
In Formbricks, create a workspace named Deployment check. The check creates and deletes its test surveys
there, so keep it separate from real data.
2
Create an API key
Go to Organization settings → API keys and create a key with write access to the Deployment check
workspace only. No organization-level access is needed.
3
Run the image
Pass the workspace id when the key has no organization access, which is the recommended setup.If you serve surveys from a separate domain, also set
FORMBRICKS_PUBLIC_URL:latest only when your app runs the latest stable release. Otherwise, use the published check image
tag matching your Formbricks version. Confirm that tag exists before scheduling the check.
Configuration
The container must be able to reach your instance. When file storage points at a bucket that only the app can
reach, the storage check reports that as a failure, because browsers would not reach it either.
Read The Results
Each check prints one line:- ✅ passed. ❌ failed, with the broken component and the next step. ⏭ skipped, because an earlier check it depends on failed. Fix the first ❌ and run again.
- The exit code is
0when nothing failed. Skipped checks do not fail the run. report/html/index.htmlis a browsable report, with a trace and screenshot for failed browser steps.report/junit.xmlis for CI systems.
Common Failures
What It Creates
Each run creates up to two surveys named[deployment-check] ... in the workspace and submits one response to
one of them. Everything is deleted at the end of the run, including when a check fails. Surveys older than one hour
that carry the prefix are deleted too, so a run that was killed does not leave data behind. The check only ever
touches surveys with that prefix.
The single test response is stored with its survey and removed with it, so it does not remain in your usage counts.