Troubleshooting Agent Assurance

Every message the console or a test can show, in the words you see it, with the cause and the fix.

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

​

Connecting a web agent

A message failed with a bad reply

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.

My endpoint rejects every request as a bad signature

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.

A message failed with a timeout

Your endpoint did not answer within 60 seconds. Answer inside the request. A message is tried three times, then marked failed.

A message failed because of a redirect

Your address answered 3xx. We never follow redirects. Give the final address in Change this agent, then prove it again.

A message failed because the reply was too large

The reply body was over 262,144 bytes. Return the words only.

It says the address points to a private or internal network

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

The bot is not reachable or never answers

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.

Check now did not find the code in the About text

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

Check connection says we have not seen your agent list our tools

Add the entry to the test copy and restart it. Many agents read the tool list once at start. See Connect our test tools.

Our tools refuse calls between tests

Expected. The tools answer only while a test run of your agent is open.

Traces are not arriving

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

Your workspace does not run its own tests yet. Ask your DeepBlocker contact to turn this on.

Self-service is off for your workspace. You can read reports and stop tests, nothing else. Write to [e-mail] with your workspace name. See What Agent Assurance does.

Agent Assurance is not turned on for your workspace.

The product itself is off, or its licence ended. Ask your DeepBlocker contact.

Only the workspace owner or an admin can do this.

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.

You are not a member of this workspace.

Your account is signed in but not listed on the workspace. Ask the owner to invite you again.

Your account needs an email address to do this.

Every action is recorded with who did it. Sign in with an account that has an email address. See Team and roles.

Too many requests. Wait a minute and try again.

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.

We could not check your access just now. Try again in a minute.

A read on our side failed, so we refused rather than guess. Wait a minute and try again.

​

Plan limits

Add an agent is greyed out: your plan allows N agents and all are in use

Remove an agent under Change this agent, or ask to add agents to your plan. See Plans and usage.

This test needs N test conversations. You have N left this month.

Plan a smaller test, or wait for the month to turn. A sweep uses its whole budget at once.

A test paused with: This workspace has used its N test conversations for the month

The next conversation could not be counted. The test resumes when the month turns or the plan grows.

Your plan does not include this channel.

The channel is not in your plan, or no test can run on it yet. See Channels.

Your plan uses the standard rules. Writing your own rules comes with the Pro plan and above.

Tick the standard rules only, or ask about Pro. See Rules.

This sweep would hold N test conversations. The most one sweep can hold is 40.

Pick fewer kinds of attack, fewer styles or a lower intensity.

​

The testing agreement

No rules of engagement recorded for this target

No testing agreement is signed for this agent. An owner or admin signs it on the Tests tab. See The testing agreement.

Rules of engagement were revoked; record and sign a new one to resume testing

DeepBlocker revoked the agreement. Sign a new one, or ask your DeepBlocker contact why.

Signed authorisation PDF not uploaded

The signed record has no PDF. For an agreement signed in the console, sign it again. For one DeepBlocker recorded, ask your contact.

Rules of engagement do not start until date

The agreement’s start date is in the future. Wait, or ask your DeepBlocker contact to change it.

Rules of engagement expired on date

The agreement ended. Sign it again on the agent’s Tests tab.

Now is outside every agreed test window

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 channel is not in the agreed scope

The agreement covers another channel. Sign it again for this one.

The endpoint is not in the agreed scope

The agent’s address changed since the agreement was signed. Sign it again; the Tests tab says so.

​

Starting and stopping

Type the agent name to confirm you want to start this test.

The name must match the agent’s name, in any case. Copy it from the top of the page.

Prove this agent is yours before you start a test.

Finish the proof on the Connection tab. See Add an agent.

Set at least one thing this agent must never do before you start a test.

Tick a standard rule or write a must-never rule on the Rules tab.

This test has already started.

The test is past the draft stage. Watch it on the Tests tab.

DeepBlocker runs this test with you.

The test was planned by DeepBlocker. You can stop it at any time; pausing, resuming and starting are for your DeepBlocker contact.

Global kill switch is on

DeepBlocker stopped every test everywhere. Wait for your DeepBlocker contact. See Safety.

Stop the tests of this agent before you change its address.

An address, test mode or removal waits for the agent’s live tests. Press Stop on each, or Stop all tests.

Your goal holds a word the attacker must never see. Write it another way.

Some words are blocked from the attacker’s instructions. Rewrite My own goal in other words.

Still stuck? See Support.