Troubleshooting

Fix common setup and runtime issues.

Use these checks first when a workflow starts but the results are not what you expect.

Install the Duku AI GitHub App on the repository.

The final results update is posted by the App, not by the workflow. Results still appear in Viewport even if the comment never updates.

Grant pull-requests: write in the job permissions: block.

You can also set Settings → Actions → General → Workflow permissions to Read and write.

Confirm that your hosting provider creates a GitHub Deployment for the pull request.

If it does not, set preview-url-source: comments and set preview-comment-author-logins to your deployment bot, such as vercel[bot].

If you already know the URL, pass exploration-url directly.

Place the workflow file under .github/workflows/.

Check that the branches: list matches the branch you actually merge into or deploy from.

Pull requests from forks cannot read repository secrets.

Duku previews require a pull request from a branch in the same repository.

If your app sits behind a firewall, WAF, or bot manager, allowlist Duku's egress IPs.

Use Firewall & WAF Allowlisting to configure the allowlist.