mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
"The provided model identifier is invalid" when using Amazon Bedrock's Claude 4.5 Haiku model #791
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jip-taku on GitHub (Nov 9, 2025).
Self Checks
Dify version
Dify Enterprise 3.5.2
Plugin version
0.0.47
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
Describe the issue
I am encountering a
ValidationException: The provided model identifier is invaliderror when attempting to use the Amazon Bedrock Claude 4.5 Haiku model within Dify Enterpirse.The issue persists across plugin versions 0.0.45, 0.0.46, and 0.0.47.Error Message
[bedrock] Error: req_id: 91d812bd08 PluginInvokeError: {"args":{"description":"[models] Error: ValidationException: The provided model identifier is invalid."},"error_type":"InvokeError","message":"[models] Error: ValidationException: The provided model identifier is invalid."}
✔️ Error log
No response
@dosubot[bot] commented on GitHub (Nov 9, 2025):
The correct model identifier for Amazon Bedrock's Claude 4.5 Haiku in the Dify plugin is
anthropic.claude-haiku-4-5-20251001-v1:0(source). This identifier was added in plugin version 0.0.43 and later, and is mapped in the plugin's configuration files. Make sure your configuration uses this exact identifier and that your plugin version is at least 0.0.43 (source). If you are still seeing the error on version 0.0.47, double-check that your model selection in the Dify UI or config matches the name "Claude 4.5 Haiku" exactly, as any typo or mismatch will cause a validation error.If you are using the correct identifier and still get the error, verify that your AWS account has access to this model in the selected region, as Bedrock will also return this error if the model is not enabled for your account.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@jip-taku commented on GitHub (Nov 9, 2025):
@dosu
I’ve double-checked the settings on my side:
In the Dify UI, the selected model is definitely Claude 4.5 Haiku — there are no typos or mismatches in the model name.
I also confirmed on the Amazon side that Claude 4.5 Haiku is available in the region I am using, so access/permission should not be the issue.
I’m currently running Dify Enterprise 3.5.2 (which corresponds to 1.8.2 for the open-source version).
Could this version difference be related to the error?
@dosubot[bot] commented on GitHub (Nov 9, 2025):
It's possible that the version difference is contributing to the error, but not because of a direct incompatibility between Dify Enterprise 3.5.2 (open-source 1.8.2) and plugin 0.0.47. Instead, recent changes in both the plugin and Dify core have made model identifier validation stricter and introduced new requirements for region-aware model IDs and credential linkage. If your database or provider/model configuration wasn't fully migrated or synced during upgrades, you might see models in the UI but get runtime identifier errors example.
Common causes include: mismatches between the plugin's expected model mapping and the Dify core's database state, missing or improperly linked credentials, or outdated provider/model records. Manual migration steps may be needed in self-hosted/offline setups to ensure all provider, model, and credential records are correctly linked details.
There is no official documentation stating that Dify 3.5.2/1.8.2 is incompatible with plugin 0.0.47, but several threads show that stricter validation logic in newer plugin versions can expose migration or configuration issues that weren't apparent before reference.
If you have already confirmed the model ID and AWS access, I recommend double-checking your provider/model/credential linkage in the database, especially if you upgraded or migrated manually. If you need step-by-step guidance for checking or fixing this, let me know your deployment details and I can help with SQL or migration commands.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@jip-taku commented on GitHub (Nov 9, 2025):
@dosu
Just an additional update:
I also tested the same setup on the SaaS version of Dify (1.9.2), and the exact same error still occurs.
So it doesn’t seem to be limited to the Enterprise 3.5.2 environment.
@dosubot[bot] commented on GitHub (Nov 9, 2025):
Thanks for the update—since the same "invalid model identifier" error happens on both SaaS and Enterprise, this rules out local config or migration issues and points to a broader problem with plugin logic, model mapping, or a recent change on the AWS Bedrock side.
The plugin is using the correct model ID for Claude 4.5 Haiku (
anthropic.claude-haiku-4-5-20251001-v1:0) and the region prefix logic matches the current codebase. The error typically means the constructed model ID (with or without a region/global prefix) doesn't match what AWS Bedrock expects or exposes in your account/region, even if the model appears available in the AWS console. This can happen if AWS changes model ID formats, region support, or cross-region inference rules, and the plugin's allowlist or logic hasn't caught up yet citation.Given that this is affecting both Dify SaaS and self-hosted, it's likely a plugin-side compatibility issue or a recent AWS-side change not yet reflected in the plugin. If you haven't already, try toggling the "cross-region" setting for the model (on/off) and test again—some Claude models only support the global prefix, others require a regional prefix, and AWS has changed this behavior before citation.
If that doesn't resolve it, this is likely a case where the plugin needs an update to its region/model mapping logic or AWS has made a change that hasn't been documented yet. Monitoring plugin updates or AWS Bedrock release notes for changes to Claude 4.5 Haiku support is the best next step.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@inaravae commented on GitHub (Nov 14, 2025):
@dosu
I am facing the exact same problem.
The problem only occurs when using Bedrock Claude 4.5 Haiku and 3.5 Haiku. No errors occur with 4.5 Sonnet or 3 Haiku.
Dify is v1.10.0-rc1, and the Bedrock plugin is v0.0.50. I changed the "Use Cross-Region Inference" setting, but it did not improve the situation at all.
@jip-taku commented on GitHub (Nov 26, 2025):
Plugin version 0.0.51
the bug is still not fixed.
@jip-taku commented on GitHub (Nov 27, 2025):
It turns out that for Claude Haiku 4.5 in the Tokyo region (ap-northeast-1), AWS requires a specific jp prefix for the inference profile, rather than the standard apac prefix that the plugin currently assigns.
@jip-taku commented on GitHub (Dec 5, 2025):
With Bedrock plugin version 0.0.54, the Claude Haiku 4.5 model works in Cross-Region Inference’s global mode.