PREMIUM_ALREADY_INVESTED
PREMIUM_ALREADY_INVESTED
Description
The single premium has already been invested, so its allocation is locked.
HTTP Status
409 Conflict
doc_url Format
<docs-base-url>/errors/premium_already_invested
Typical Cause
The allocation was submitted after investment processing completed.
Example
json
{
"errors": [{
"code": "PREMIUM_ALREADY_INVESTED",
"message": "Premium request with id: '…' was already invested",
"doc_url": "https://docs.example.com/errors/premium_already_invested"
}]
}How To Fix
Do not retry allocation submission for an invested single premium. Use a switch to change the compartment's invested position.