Redeploy

Prerequisites

• App with login, with a Vercel project linked. See Signing secret.
• MODIFEE_SECRET already written on Vercel. The status is "MODIFEE_SECRET set on Vercel ✓". The banner is what asks for the redeploy.
• At least one production deployment on that Vercel project.

Steps

Vercel applies environment variables on the next deployment. Writing MODIFEE_SECRET does not restart the current one. Until production is deployed again, the site keeps signing with the previous value, and Modifee checks tokens against the new one.

The status line can already say "MODIFEE_SECRET set on Vercel ✓". That means the variable is stored. The banner under Signing secret says "The secret is on Vercel, but it only applies on the next deployment." The shorter line is "Redeploy required — the secret applies on the next deployment."

1. Press Redeploy now. The label becomes "Deploying…".
2. Modifee starts a new Production deployment from the latest production deployment. Preview already has the variable. A preview deployment picks it up the next time that preview is deployed. This button does not redeploy previews.
3. Wait on the banner. It checks the deployment every few seconds.

Open in Vercel opens that project's deployments.

Permission missing (403)

If Vercel returns 403, the banner says "Redeploy from Vercel or push a commit." The server reason is "Missing deployment permission."

1. Press Update integration permissions. That opens the installed Modifee integration on Vercel.
2. Allow Deployments for the integration.
3. Return to Signing secret and press Redeploy now again.

You can also redeploy from Vercel, or push a commit, as the banner says. A production deployment whose start time is after the last push counts as deployed.

Verify

The banner turns green and says "Deployed ✓ — the widget is live".

That line means the latest READY production deployment started at or after the last MODIFEE_SECRET push. The status line "MODIFEE_SECRET set on Vercel ✓" can show before this, as soon as the variable is stored.

Open the production site while signed in. The widget should accept the token. A token signed before Regenerate still fails.

Troubleshooting

• "Redeploy from Vercel or push a commit." with Update integration permissions. The Deployments permission is missing (HTTP 403, "Missing deployment permission.").
• "The deployment failed." The deployment readyState was ERROR or CANCELED, or Modifee could not start one.
• "There is no production deployment to redeploy." The banner still shows "The deployment failed." Create a production deployment on Vercel, then press Redeploy now.
• "This project is not linked to a Vercel project we can update."
• "That Vercel project was not found."
• The banner stays on "The secret is on Vercel, but it only applies on the next deployment." Production has not finished a deployment since the push. Press Redeploy now or Open in Vercel.
• Secret and redeploy.