Test your deployment trigger
Use Test Deployment Trigger to send a test request to your deploy hook and confirm your host accepts it before you publish real content.
After you configure a deployment method, Test Deployment Trigger sends a test request to your deploy hook and records the response. Run it to confirm your host accepts the trigger before you publish real content.
Who this is for
Developers, and Owners or Admins who set up deployment for a project.
Before you start
- You have chosen a deployment method and saved its details. See Configure a deployment trigger.
- The method is a deploy hook (Vercel, Netlify or Cloudflare Pages). Git-connected and Manual send no trigger.
Test the trigger
On the project's Deployment Setup page:
- Find the Test Deployment Trigger action.
- Run it. Acrosite sends a test request to your configured trigger.
- Check the result. The confirmation "Deployment trigger test succeeded." appears, and the Provider panel shows the Last test time. If the test failed, the error is shown under the panel instead.
Important
A successful test confirms your host accepted the request. It does not confirm the build finished: a test trigger has no commit, so Acrosite shows no build status for it. Check your host's dashboard.
What happens next
Once the test succeeds, you are ready to publish. From then on, each publish commits your content and then sends this trigger, and every trigger is recorded in Deployment Logs.
Troubleshooting
- The test action is unavailable. Configure and save a deployment method first; the test is available once a provider is set up.
- The test failed. Re-copy the deploy hook URL from your host (hooks can be regenerated or revoked) and save it again, then re-test. Make sure it is complete and uses
https://.