Troubleshooting workflow failures

Use this article when a workflow stops, fails validation, asks for missing information, or cannot start because of product state.

Common symptoms

• The assistant asks you to select a repository.
• The assistant asks for missing requirements or clarification.
• A quota, billing, or token message blocks new work.
• Validation fails after code, tests, linting, browser inspection, or another tool step.
• A tool is unavailable for the selected repository or current workflow.

Fix the most common causes

1. Confirm that the active chat has the right repository selected.
2. Include the branch, issue, pull request, or file names that matter.
3. Answer any clarification question with the missing requirement or constraint.
4. If the message mentions quota, tokens, billing, or send availability, check Settings > Usage and Settings > Billing.
5. Review the progress updates and validation output shown by the assistant.
6. Retry only after you have corrected the missing context, quota issue, or repository selection.

When validation fails

Validation output is useful support context. Include the visible error summary, command name, test name, or browser step when you ask for help.

If the failure happened after code changes, ask the normal workspace flow to investigate or fix the code. If the problem is account, billing, access, quota, or product behavior, ask for support in chat.

Contact support

Create a support ticket from chat when the issue needs Polka Codes support or staff investigation. A ticket can include the current page, selected repository, and recent relevant workflow context, which helps support understand where the failure happened.