Troubleshooting¶
Run into issues? Use this checklist to diagnose common problems.
Sync Failures¶
- Check Project → Activity for the latest sync job. Errors include file paths and validation messages.
- Validate YAML locally with
kiket workflows validate. - Ensure the GitHub token has
repoandadmin:repo_hookscopes and the branch exists.
Missing Boards or Columns¶
- Confirm the board YAML includes
workflowand matching column keys. - Verify the workflow file defines the states referenced by the board.
- Remove stale boards in the UI—Kiket will recreate them on the next sync.
Webhook Errors¶
- Inspect delivery logs for HTTP status codes. 401/403 indicate signature or auth issues.
- Regenerate webhook secrets if they might be compromised.
- Ensure your endpoint responds within 10 seconds; otherwise Kiket retries and may eventually disable the webhook.
Extension Fails to Install¶
- Validate the manifest schema (use the CLI or the manifest editor in the UI).
- Check that the host URL is reachable over HTTPS.
- Confirm settings fields marked
requiredhave values supplied during installation.
API Authentication Issues¶
- Verify token scopes match the endpoint you are calling.
- For extensions, ensure you are using the installation-specific API key, not a user token.
- Review audit logs to confirm the token has not been revoked.
Analytics Discrepancies¶
- Re-run DSAL queries with
--explainto inspect the generated SQL. - Ensure metrics reference the correct project or timeframe.
- Verify that sync jobs processed all relevant repositories.
Diagnostics Dashboards¶
- Extension invocations: Go to Admin → Extensions → Invocations and click View in the Diagnostics column to inspect payloads, missing secrets, and remediation guidance for every failing webhook.
- Definition repos: Open Settings → Workflow Repositories →
. The page now surfaces a Definition diagnostics alert with actionable steps and links to the relevant YAML files. - CLI summary: Run
kiket doctor run --extensions --workflowsto fetch the same diagnostics over the API, complete with hints and admin links for quick follow-up.
Still stuck? Reach out to support via Slack or email and include logs, timestamps, and repository references.