Sometimes, even the coolest features hit a roadblock — and that’s exactly what happened with Oracle APEX’s out-of-the-box Generate Text with AI & Chatbot dynamic actions when used with Cohere API. If you’ve tried setting it up recently and saw weird errors, you’re not alone.
![]() |
Cohere Integration Fails in Oracle APEX versions less than 24.2.9 |
If you would like to visualize this, check out the below YouTube video:
⚠️ The Problem
While configuring Cohere inside APEX, I ran into the following error message:
unknown field: parameter 'chat_history' is not a valid field
Previously, APEX used to send parameters like connectors
and chat_history
to Cohere’s v1 API endpoint. But as of September 15, 2025, these fields were officially removed from Cohere’s API, making the existing integration fail. Ouch!
🔧 The Fix (officially)
Oracle has already acknowledged the issue, and the patch is baked into APEX 24.2.9 and later. Once you’re on that release (or higher), your Cohere service connection will work again — no code changes required.
As of today, however, the fix isn’t yet available in the General Cloud Service tier. So don’t panic if your free-tier workspace still throws errors — it’s not you, it’s the API.
⏳ Current Limitation
If you’re on 24.2.8 or below, the “Generate Text with AI” dynamic action will continue to fail with Cohere. The safest bet is either:
- Wait until your environment is patched to 24.2.9+
- Or, roll your own custom
apex_web_service.make_rest_request
call without the deprecated fields
🎥 Workaround: Replicating “Generate Text” Yourself
Until the fix reaches your instance, you can directly call Cohere’s Chat API and replicate the Generate Text dynamic action on your own. I’ve recorded a step-by-step video showing how to wire this up and still keep your AI features running inside APEX.
Watch the demo here:
<not yet recorded - TBA>✅ Wrap-up
So to summarize:
- Error: Cohere’s API dropped
connectors
andchat_history
- Fix: Shipped in APEX
24.2.9+
- Current Status: Not yet available in Free Cloud tiers (as of this writing)
- Workaround: Use the Chat endpoint directly until your workspace is upgraded
If you’re facing this too, relax — it’s not your code, and you don’t need to debug endlessly. Just wait for the patch, or try the DIY route with custom REST calls in the meantime. 😉
Stay tuned — in my next post I’ll show how to wire Cohere responses into actual JavaScript function calls in APEX for real-world actions. Until then, happy developing!
data:post.title

Written by
Published on October 01, 2025
No comments: