---
url: /errors/single_premium_request_not_pending.md
---
# `single_premium_request_not_pending`

`single_premium_request_not_pending`

## Description

The single premium request cannot be acted upon because it is no longer in `PENDING` status.

## HTTP Status

`409 Conflict`

## `doc_url` Format

The `doc_url` value is an absolute URL and changes by environment:

`<docs-base-url>/errors/single_premium_request_not_pending`

## Notes

* The `POST /v1/premium-scheduling/single-premium-requests/:id/cancel` endpoint can surface this code when the repository rejects the status transition.
* The details endpoint still has a defensive branch for this code, but current repository behavior maps missing rows to `single_premium_request_details_not_found` instead, so the `404` path is not emitted today.
* Cancellation precondition failures can also return the generic `conflict` code. See `/errors/conflict`.

## Typical Causes

* The request was already executed or cancelled.
* The request was transitioned out of the pending state by a previous operation.

## How To Fix

1. Check the current status of the single premium request.
2. For cancellation, also ensure the request is still eligible to be cancelled.
3. For details, use a valid request ID and expect `single_premium_request_details_not_found` when the row is missing.