Errors
409 - addon already enabled
What happened
The capability is already enabled. Sending the same enable request again conflicts with its current state.
- Read the current configurationFind the add-on that returned the conflict.
- Compare the requested stateCheck that the enabled capability is the intended one.
- Continue with the featureUse the active configuration once it matches.
Request that triggers it
Re-enabling an addon that's already on.
curl -X POST "https://$OC_HOST/v1/tenants/$OC_TENANT/addons" \
-H "Authorization: Bearer $OC_TOKEN" \
-H "Content-Type: application/json" \
-d '{"addon": "ask"}'Read the response
{
"error": "addon_already_enabled",
"message": "addon 'ask' is already enabled for this tenant",
"retry": false
}Fix the request
- Read the instance’s current capability state.
- Check that it matches the requested configuration.
- Treat an already-satisfied setup step as complete.
- Continue with the feature operation.
Keep in mind: Do not repeatedly enable or buy the capability to resolve this response.
Common causes
- Provisioning script run twice in CI.
- Dashboard click that re-fired through a stale tab.
- Migration that enabled the addon manually, then a Terraform run that tried to enable it again.
- Two team members enabling the same addon from different sessions.
Continue
See error handling and retries, or return to error examples.