fix: re-raise InputCheckError/OutputCheckError in non-streaming run functions

[VANDRANKI]

Summary

The documentation shows callers using try/except OutputCheckError around agent.run() and agent.arun() to handle output validation failures. This pattern was silently broken: the four non-streaming entry points (_run, _arun, _continue_run, _acontinue_run) caught the exception, logged it, and returned the run response as if nothing went wrong - the caller's except block was never reached.

Root cause: the except clause ended with return run_response instead of raise.

Changes

• libs/agno/agno/agent/_run.py: In the except (InputCheckError, OutputCheckError) block of each non-streaming function, replace return run_response with raise.
  • def _run (~line 659)
  • async def _arun (~line 1754)
  • def _continue_run (~line 3064)
  • async def _acontinue_run (~line 3862)

Session cleanup and storage are performed before the re-raise, so persistence is unaffected.

What stays the same

The streaming variants (_run_stream, _arun_stream, _continue_run_stream, _acontinue_run_stream) already surface the error correctly by yielding a RunErrorEvent to the caller's event loop. Those are unchanged.

Reproduces fix for issue #7414

Before:

try:
    result = await agent.arun("What is the capital of France?")
    print(result.content)  # prints "Paris" - validation failure ignored
except OutputCheckError as e:
    print(f"Validation failed: {e}")  # never reached

After:

try:
    result = await agent.arun("What is the capital of France?")
    print(result.content)
except OutputCheckError as e:
    print(f"Validation failed: {e}")  # now correctly raised

Fixes #7414

[github-actions]

PR Triage

A few things to address before this PR can be reviewed:

Missing tests: This PR modifies source code but does not include any test changes. Please add or update tests to cover your changes.

---

Possible duplicate: The following open PRs also reference the same issue(s):

• fix(agent): propagate OutputCheckError to caller #7418 (also references issue [Bug] OutputCheckError not raised to caller in post-hook output validation — caught internally and logged instead #7414)

If this is intentional, please explain in your PR description why this approach is preferred. Otherwise, consider collaborating on the existing PR instead.

---

This PR has been automatically closed. There is already an open PR addressing this issue. If you believe your contribution is valuable, please comment on the original issue explaining your approach and why it might be preferred. A maintainer can reopen this PR if appropriate.