Technical Support
Having issues with the CLI, SDK, or dashboard? Describe your problem below and our engineering team will help.
Common Questions
Ensure `reshot setup` completed in your project, your repo has a valid `reshot.config.json`, and you have write permissions. Check your network connection, then retry with `RESHOT_DEBUG=1 reshot publish` if you need more detail.
Verify your publish step is still running after captures are updated and that the project is using a hosted delivery workflow. If comments or review signals stopped appearing, send us the project name and the latest pipeline run so we can trace it.
This is usually caused by asset processing delays or an interrupted publish. Check your latest publish with `reshot status --jobs`, then try publishing again. If a visual stays stuck, send us the project name and publish timestamp so we can trace it.
Start with `reshot status --config` to inspect the active project configuration, then retry the failing command with `RESHOT_DEBUG=1` for detailed logs. If your project uses the certified target contract, `reshot doctor target` is the fastest way to catch route, readiness, or auth mismatches before you publish.