You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the OpenAI API key is not set, he AI search feature does not work, as expected. Still the feature is visible and the user can try using it, resulting in errors code 500 in the backend (especially the api-gateway) and in a "forever spinning" waiting icon on the WebUI.
2024-02-07 00:30:36 2024-02-06T23:30:36.744Z [API_GATEWAY]: Error: Request failed with status code 401
2024-02-07 00:30:36 at /usr/local/api-gateway/node_modules/@guardian/common/dist/mq/nats-service.js:140:28
2024-02-07 00:30:36 at AISuggestions.<anonymous> (/usr/local/api-gateway/node_modules/@guardian/common/dist/mq/nats-service.js:55:33)
2024-02-07 00:30:36 at Generator.next (<anonymous>)
2024-02-07 00:30:36 at fulfilled (/usr/local/api-gateway/node_modules/@guardian/common/dist/mq/nats-service.js:5:58)
2024-02-07 00:30:36 at runMicrotasks (<anonymous>)
2024-02-07 00:30:36 at processTicksAndRejections (node:internal/process/task_queues:96:5)
2024-02-07 00:30:36 [Nest] 19 - 02/06/2024, 11:30:36 PM ERROR [ExceptionsHandler] Request failed with status code 401
2024-02-07 00:30:36 Error: Request failed with status code 401
2024-02-07 00:30:36 at /usr/local/api-gateway/node_modules/@guardian/common/dist/mq/nats-service.js:140:28
2024-02-07 00:30:36 at AISuggestions.<anonymous> (/usr/local/api-gateway/node_modules/@guardian/common/dist/mq/nats-service.js:55:33)
2024-02-07 00:30:36 at Generator.next (<anonymous>)
2024-02-07 00:30:36 at fulfilled (/usr/local/api-gateway/node_modules/@guardian/common/dist/mq/nats-service.js:5:58)
2024-02-07 00:30:36 at runMicrotasks (<anonymous>)
2024-02-07 00:30:36 at processTicksAndRejections (node:internal/process/task_queues:96:5)
Requirements
Remove the "Search with AI" tab if AI search is not enabled in the backend.
Definition of done
Users can see "Search with AI" tab and use that function only if the backend is correctly configured to use the OpenAI APIs.
Acceptance criteria
The fix is present in a new Guardian release.
The text was updated successfully, but these errors were encountered:
Problem description
If the OpenAI API key is not set, he AI search feature does not work, as expected. Still the feature is visible and the user can try using it, resulting in errors code 500 in the backend (especially the api-gateway) and in a "forever spinning" waiting icon on the WebUI.
Requirements
Remove the "Search with AI" tab if AI search is not enabled in the backend.
Definition of done
Users can see "Search with AI" tab and use that function only if the backend is correctly configured to use the OpenAI APIs.
Acceptance criteria
The fix is present in a new Guardian release.
The text was updated successfully, but these errors were encountered: