What to Do When a Prompt Is Blocked

Why Zeuslock blocks a send, the simple steps to fix it and get going again, and a couple of worked examples. A block protects you from an accidental leak.

Sometimes a red “Send blocked — critical data detected” banner appears and your message is not sent. This happens when your prompt contains data your organization never allows in AI tools — like API keys, passwords, or customer card numbers. If you attached a sensitive file, it is removed too.

What to do

  1. Read the banner — it tells you what was found.
  2. Remove or replace the sensitive part — delete the secret, or describe your problem without it.
  3. Send again — the cleaned prompt goes through.
  4. Need that data for a real reason? Ask your security or admin team — they set the rules and can help.

Examples

  • Pasting an AWS key into a debugging question → blocked. Fix: remove the key and paste only the error message.
  • Uploading a spreadsheet of customer card numbers → the file is removed. Fix: delete the sensitive column, or ask your admin for approval.

Remember

A block is not a punishment — it is protecting you and the company from an accidental leak. Rewriting without the sensitive part is almost always all you need.