Skip to main content
Find the words you see in the console or in your own logs, open the row, and follow the fix.

Connecting a web agent

Your endpoint answered, but not with { "reply": "..." }. The reply must be a JSON object, reply must be a string that is not blank, and messageId may be left out or null. Check a proxy is not answering with HTML. See Connect a web agent.
The signed text is <t>.POST <path and query> then one line feed then the raw body, with the key from Show signing key. Use the path, not the full address, and the body bytes as received. Run the curl sample on the connect page; if it passes, we pass.
Your endpoint did not answer within 60 seconds. Answer inside the request. A message is tried three times, then marked failed.
Your address answered 3xx. We never follow redirects. Give the final address in Change this agent, then prove it again.
The reply body was over 262,144 bytes. Return the words only.
The name now resolves to a private address, so no message is sent. Point it at a public address. We check before every message.

Connecting a Telegram bot

Our attacker writes as a Telegram user. Send the bot a private message from a personal account it has never seen. If it stays silent for 4 minutes, check it is running and answers new users. See Connect a Telegram bot.
Open https://t.me/<bot name>; the About text must show the code. @BotFather can take a minute to publish. Then press Check now again.

Our test tools and activity logs

Add the entry to the test copy and restart it. Many agents read the tool list once at start. See Connect our test tools.
Expected. The tools answer only while a test run of your agent is open.
The exporter gets 401 for a wrong key, 403 when no test is running, 429 when it sends too fast. Only 429 and 503 should be retried. See Send activity logs.

The switch, your role and your account

Self-service is off for your workspace. You can read reports and stop tests, nothing else. Write to hello@deepblocker.ai with your workspace name. See What Agent Assurance does.
The product itself is off, or its licence ended. Ask your DeepBlocker contact.
Signing the agreement, starting a test and resuming a paused test need the owner or admin role. Ask one of them, or see Team and roles.
Your account is signed in but not listed on the workspace. Ask the owner to invite you again.
Every action is recorded with who did it. Sign in with an account that has an email address. See Team and roles.
More than 30 changes, 6 checks or 120 reads in one minute from your account. Wait a minute. Stops have their own limit and still work.
A read on our side failed, so we refused rather than guess. Wait a minute and try again.

Plan limits

Remove an agent under Change this agent, or ask to add agents to your plan. See Plans and usage.
Plan a smaller test, or wait for the month to turn. A sweep uses its whole budget at once.
The next conversation could not be counted. The test resumes when the month turns or the plan grows.
The channel is not in your plan, or no test can run on it yet. See Channels.
Tick the standard rules only, or ask about Pro. See Rules.
Pick fewer kinds of attack, fewer styles or a lower intensity.

The testing agreement

No testing agreement is signed for this agent. An owner or admin signs it on the Tests tab. See The testing agreement.
DeepBlocker revoked the agreement. Sign a new one, or ask your DeepBlocker contact why.
The signed record has no PDF. For an agreement signed in the console, sign it again. For one DeepBlocker recorded, ask your contact.
The agreement’s start date is in the future. Wait, or ask your DeepBlocker contact to change it.
The agreement ended. Sign it again on the agent’s Tests tab.
The agreement limits the hours tests may run. An agreement signed in the console allows any hour; one DeepBlocker recorded may not. Wait for the window, or ask your contact.
The agreement covers another channel. Sign it again for this one.
The agent’s address changed since the agreement was signed. Sign it again; the Tests tab says so.

Starting and stopping

The name must match the agent’s name, in any case. Copy it from the top of the page.
Finish the proof on the Connection tab. See Add an agent.
Tick a standard rule or write a must-never rule on the Rules tab.
The test is past the draft stage. Watch it on the Tests tab.
The test was planned by DeepBlocker. You can stop it at any time; pausing, resuming and starting are for your DeepBlocker contact.
DeepBlocker stopped every test everywhere. Wait for your DeepBlocker contact. See Safety.
An address, test mode or removal waits for the agent’s live tests. Press Stop on each, or Stop all tests.
Some words are blocked from the attacker’s instructions. Rewrite My own goal in other words.
Still stuck? See Support.