Deploy hooks are creating jobs but no deployments

Help
1

Issue: Deploy hooks are creating jobs but deployments are not appearing in the dashboard or executing builds.

Project Details:

  • Project Name: localplus-admin-dashboard

  • Repository: dhsg225/localplus-super-app

  • Root Directory: admin (correctly configured)

  • Framework: Vite (auto-detected)

Configuration Status:

  • :white_check_mark: Git repository connected properly

  • :white_check_mark: Root directory set to admin

  • :white_check_mark: Environment variables configured

  • :white_check_mark: Build settings correct (npm run build, dist output)

  • :white_check_mark: Deploy hook created and working

Problem Details:

  1. Deploy hooks are successfully creating jobs with PENDING status

  2. Two separate job IDs created: vYvzCB0haVuZmd7KPcsL and U4Xl7vIIi2FAeDmyjmnW

  3. Both returned successful responses with “state”: “PENDING”

  4. However, no deployments appear in the Deployments tab at all

  5. Dashboard still shows “No Production Deployment”

  6. Filtering shows “No deployments match the current filters”

Deploy Hook URLs Used:

text

Apply

https://api.vercel.com/v1/integrations/deploy/prj_8Vzpi2zRHJN2KQ4HpANQJRgvXMyA/6O70C389Qs

Expected Behavior:

Deploy hook should trigger a build and deployment visible in the Deployments tab.

Actual Behavior:

Jobs are created but no builds start and no deployments appear in dashboard.

Question for Support:

Why are deploy hook jobs being created successfully but not triggering actual builds or appearing in the deployment history?

3

Can you share a job ID?

4

Most Recent Job ID: U4Xl7vIIi2FAeDmyjmnW

Previous Job ID: vYvzCB0haVuZmd7KPcsL

Both were created for the localplus-admin-dashboard project and both show as PENDING but never progressed to actual deployments.

5

Hi Swarnava - did you need any other info ?

thanks

6

Sorry I was offline yesterday.

I can see following error occurred when deploying:

api call failed with “Environment Variable “VITE_SUPABASE_URL” references Secret “supabase-url”, which does not exist.”

Based on the error logs, it seems that your project is utilizing legacy secrets. It is possible that your project is using vercel.json file which has the secrets defined. You can add the Environment variables in the Dashboard > Project Settings, could you please remove any secrets from the vercel.json file and check if it resolves the issue? For more detailed information, you can refer to this guide: Configuring projects with vercel.json

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.