Troubleshooting

Solve common Kluck errors

Use a focused checklist for connection, Brand DNA, Chat, routine, permission, credit, and payment issues.

7 min readUpdated July 18, 2026

Connected store or advertising data is missing

  • Open Settings → Connectors and confirm the relevant source shows as connected.
  • Verify the correct Shopify store and Meta ad account are selected.
  • Reconnect a source if its live connection test fails.
  • Allow time for the workspace context to refresh, then retry the request in a new Chat.
  • Contact support if a successful reconnection still produces no current data.

Brand DNA is missing or still generating

  • Add a storefront URL or connect Shopify so Kluck has a brand source.
  • Open Settings → Brand DNA and refresh after the generation status has had time to update.
  • Regenerate after connecting better source data.
  • If generation repeatedly ends without a Brand DNA result, contact support.

Chat cannot answer a live store or ad question

  • Confirm the relevant source is connected.
  • Allow time for connected data to refresh after setup or an account change.
  • State the desired time period and account in the request.
  • Start a new chat if the existing conversation contains stale assumptions.

Insufficient credits or workspace allowance reached

  • Open Settings, then Usage, and review both plan and additional balances.
  • Check whether the active workspace has a monthly allowance.
  • Ask an owner or admin to buy credits or adjust the workspace allowance.
  • After payment, wait briefly for the balance to update and refresh the page.

You do not have permission

  • Confirm you are in the correct organization and workspace.
  • Check whether the action requires owner or admin access.
  • Ask an admin to edit Brand DNA, manage Brand Avatars, or resolve a protected approval.
  • Ask an owner or admin to manage plans, purchases, and organization access.

Still need help?

Send the team a useful support request.

Include the workspace, affected feature, what you expected, and the error you saw. Never include passwords or access tokens.

Contact support

Related guides

More in Troubleshooting