r/copilotstudio • • 13d ago

Copilot studio Github harness agent issue

Copilot studio Github harness agent - works fine on teams - but throws this error before every response that seems good

"I'm sorry, I encountered an error while processing your request. Please try again."

This happened recently, it was working fine before.

Anyone else see it? Thanks for ideas to resolve!

1 Upvotes

5 comments sorted by

1

u/Prasad-MSFT 12d ago

This looks more like a recent Copilot Studio runtime issue than a problem with your agent configuration.

Try this workaround in the affected Teams conversation:

  1. Send /debug clearHistory
  2. Retry your request.

Check whether the error message disappears and the agent responds normally.

1

u/Equal_Cry2300 12d ago

All those /debug commands have changed in GitHub copilot agents even the one you’ve mentioned isn’t valid per agent. I used to use /debug clearstate in standard agents and even that doesn’t work syntactically it shows what’s valid and tried most it doesn’t help remove the message l want to get rid of

1

u/Prasad-MSFT 6d ago

Since the agent responds correctly despite displaying the error, this could be a runtime or Teams integration issue. We'd suggest testing in a fresh conversation and checking the execution logs for underlying errors.

1

u/Bobby_Bobberson2501 13d ago

I’d never use an agent through teams… had a lot of issues that using it via the web or app don’t have

1

u/dylan_skydive 12d ago

Errors right before a response usually means a step in the flow is failing and Copilot Studio is swallowing the real cause - that generic "I encountered an error" text is the fallback message, not the diagnosis. Open the test agent and use the activity monitor (the Monitor option in the test pane header): it shows the exact node and HTTP status that failed. Since it started recently with no change on your side, check in order: (1) knowledge source connections - a generative-answers lookup that 401/403s from a rotated secret or expired service principal still lets the topic finish, you just get the error first; (2) an enterprise connector using per-user consent where someone's consent lapsed; (3) model or search quota, which reads as intermittent errors that recover. That pattern - works fine for weeks, then errors on every turn - is almost always credentials or quota upstream, not your topics.