Use clients error type when figuring out the errors. [#3508935]

Problem/Motivation

Currently we are looking at the error message we get back from the LLM and try to map that to our exceptions, however the client has a better method for it here: https://github.com/openai-php/client/blob/main/src/Exceptions/ErrorExcep...

We should map to this instead.

Proposed resolution

Map to the different Exceptions to different error types "insufficient_quota" etc. in OpenAI's responses.
Do it in one method that can be overriden.

Comment	File	Size	Author
#2	3508935-improved-error-handling-applied-2.patch	7.16 KB	pinesh

Issue fork ai_provider_openai-3508935

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

3508935-use-clients-error changes, plain diff MR !51
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

25 February 2025 at 16:21

marcus_johansson created an issue. See original summary.

Comment #2

pinesh commented 3 September 2025 at 06:51

Status	File	Size
new	3508935-improved-error-handling-applied-2.patch	7.16 KB

Implemented improved error handling using OpenAI client's built-in error type detection. The patch maps specific OpenAI error types
(insufficient_quota, billing_not_active, rate_limit_exceeded) to appropriate AI module exceptions while maintaining backward compatibility
with legacy string matching. Ready for review and testing.