fix(write-api): Update Cloud Dedicated outside-retention failure to HTTP 422

Author: savage-engineer

api-docs/cloud-dedicated/v2/ref.yml

@@ -703,6 +703,13 @@ paths:
               schema:
                 $ref: '#/components/schemas/LineProtocolLengthError'
           description: Write has been rejected because the payload is too large. Error message returns max size supported. All data in body was rejected and not written.
+        '422':
+          description: |
+            Unprocessable Entity.
+
+            The request contained data outside the bucket's retention window, causing InfluxDB to reject the batch and write no data.
+
+            The response body contains details about the [rejected points](/influxdb/cloud-dedicated/write-data/troubleshoot/#troubleshoot-rejected-points).
         '429':
           description: Token is temporarily over quota. The Retry-After header describes when to try the write again.
           headers:

content/influxdb/cloud-dedicated/write-data/troubleshoot.md

@@ -56,8 +56,9 @@ The `message` property of the response body may contain additional details about
 | `400 "Bad request"`           | error details about rejected points, up to 100 points: `line` contains the first rejected line, `message` describes rejections line | If request data is malformed                                                                                                                                                                                                                                                                                                                                                     |
 | `401 "Unauthorized"`          |                                                                                                                                     | If the `Authorization` header is missing or malformed or if the [token](/influxdb/cloud-dedicated/admin/tokens/) doesn't have [permission](/influxdb/cloud-dedicated/reference/cli/influxctl/token/create/#examples) to write to the database. See [examples using credentials](/influxdb/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb) in write requests. |
 | `404 "Not found"`             | requested **resource type** (for example, "organization" or "database"), and **resource name**                                      | If a requested resource (for example, organization or database) wasn't found                                                                                                                                                                                                                                                                                                     |
+| `422 "Unprocessable Entity"`  | `message` contains details about the error                                                                                          | If the data isn't allowed (for example, falls outside of the bucket's retention period).
 | `500 "Internal server error"` |                                                                                                                                     | Default status for an error                                                                                                                                                                                                                                                                                                                                                      |
-| `503 "Service unavailable"`     |                                                                         | If the server is temporarily unavailable to accept writes. The `Retry-After` header contains the number of seconds to wait before trying the write again.
+| `503 "Service unavailable"`   |                                                                                                                                     | If the server is temporarily unavailable to accept writes. The `Retry-After` header contains the number of seconds to wait before trying the write again.
 
 The `message` property of the response body may contain additional details about the error.
 If your data did not write to the database, see how to [troubleshoot rejected points](#troubleshoot-rejected-points).