Deployed Sol 6.1 - getting the "I'm sorry, but I cannot assist with that request" response frequently when turning on reasoning

Question

Deployed Sol 6.1 - getting the "I'm sorry, but I cannot assist with that request" response frequently when turning on reasoning

GS 430

Deployed gpt-sol 6.1 to azure foundry - getting the "I'm sorry, but I cannot assist with that request" response frequently when turning on reasoning and combining it with web search with the responses API

Anyone else having issues with this ?

Sai Kiran Mudavath 10 Reputation points Microsoft External Staff Moderator

2026-10-01T06:21:20.9266667+00:00
Hi @GS ,

Thank you for reporting this behavior.

The message "I'm sorry, but I cannot assist with that request" can occur for several reasons, including content filtering/guardrails, tool execution issues, or other transient service-side conditions. Based on the information provided, it is not yet possible to determine the exact cause.

Since the issue occurs when using reasoning together with web search through the Responses API, could you provide the following details?

A sample request (with any sensitive information removed).

Whether the response includes any content_filter_results or incomplete_details fields.

The API version being used.

Whether the issue is consistently reproducible or only occurs intermittently.

Any trace information from Azure AI Foundry for an affected run.

In the meantime, please review:

Response details for content filtering indicators.

Any tool or web search execution failures in the run trace.

Whether any HTTP 429 or other errors are being returned around the time the issue occurs.

This information will help determine whether the behavior is related to content filtering, tool execution, throttling, or another service condition.

Thank you!

Your answer

Sai Kiran Mudavath 10 Reputation points Microsoft External Staff Moderator

2026-10-01T06:21:20.9266667+00:00

Hi @GS ,

Thank you for reporting this behavior.

The message "I'm sorry, but I cannot assist with that request" can occur for several reasons, including content filtering/guardrails, tool execution issues, or other transient service-side conditions. Based on the information provided, it is not yet possible to determine the exact cause.

Since the issue occurs when using reasoning together with web search through the Responses API, could you provide the following details?

A sample request (with any sensitive information removed).

Whether the response includes any content_filter_results or incomplete_details fields.

The API version being used.

Whether the issue is consistently reproducible or only occurs intermittently.

Any trace information from Azure AI Foundry for an affected run.

In the meantime, please review:

Response details for content filtering indicators.

Any tool or web search execution failures in the run trace.

Whether any HTTP 429 or other errors are being returned around the time the issue occurs.

This information will help determine whether the behavior is related to content filtering, tool execution, throttling, or another service condition.

Thank you!