HSX_E_PROJECT_DEPLOY_BLOCKED

01 · Meaning

What this error means

HubSpot refused to deploy the build because one or more component changes require explicit force approval. Nothing was deployed.

When this error stops a command, hs-x exits with code 1. With --json, the failure is reported as a structured error whose code field is HSX_E_PROJECT_DEPLOY_BLOCKED — stable to match on in scripts and agents.

02 · Causes

Likely causes

• The build removes or replaces a deployed component that HubSpot protects from accidental deletion
• HubSpot returned one or more blocking component warnings for the requested build

03 · Fix

How to fix it

• Read every component warning in the command output and confirm that each removal or replacement is intentional
• Restore unintended component changes and upload a corrected build
• Only after reviewing the warnings, retry the same build with hs-x project deploy --build <id> --force

Still stuck? Re-run the command with --debug for the wire-level detail, or hs-x doctor to check accounts, link state, and connectivity in one pass.