Infos:
- Used Zammad version: 7
- Used Zammad installation type: any
- Operating system: Ubuntu 22
- Browser + version:
Expected behavior:
-
After successfully configuring the Custom (OpenAI Compatible) provider, AI features such as Ticket Summarization should work seamlessly.
-
The AI provider should generate a summary and display it in the ticket interface
Actual behavior:
• While the initial connection test/setup succeeds, the actual usage of AI features (e.g., clicking “Summarize”) fails.
• The Zammad production log shows a 400 Bad Request from the API provider.
• The error returned is: Invalid JSON payload received. Unknown name “store”: Cannot find field.
• It appears that Zammad successfully validates the endpoint during setup (likely via a simple handshake), but the specific payload sent during summarization tasks includes the “store” parameter, which is rejected by the Google Gemini OpenAI-compatible API.
Steps to reproduce the behavior:
- Successfully configure a Custom (OpenAI Compatible) provider using the Google Gemini API endpoint.
- Open any ticket with existing articles.
- Click on the AI Summarize button .
The process fails, and the logs confirm that the “store” field in the JSON payload is the cause of the INVALID_ARGUMENT error