Secured Scripts Execution
Overview
Backend scripts always run through Protected Execution: a dedicated external Companion App executes them, isolating script execution from the shared Forge backend context.
The previous Unsecured Execution mode, which ran scripts directly in the shared Forge backend context, has been removed. Without a configured Companion App, backend script execution is disabled — the affected modules show an "Action Required" banner and their scripts do not run.
If you are upgrading from a version that relied on unsecured execution, configure the Companion App before your scripts are expected to run again.
Affected Modules
- Web Triggers
- Scheduled Jobs
- Custom Fields
- Workflow Extensions
Other modules — Fragments, Gadgets, Macros, and the Script Console — run in the browser with the current user's permissions and are not affected by this setting.
Follow this guide to configure Protected Execution via the dedicated companion app.
Configuration
Follow the video guide:
Or follow the step-by-step guide in Script Master: Sandbox to build, install, and configure the companion app.
Open Script Master → Settings → Protected Scripts Execution and paste the Companion App's web trigger URL. The status should change from Unsecured Execution — which now means "no Companion App configured, backend scripts are blocked" — to Secured Execution.
Invalid Configuration status appears when the companion app is installed but not properly configured.
To resolve this issue:
- Reinstall the latest version of the companion app.
- Follow the configuration guide to set it up correctly.