diff --git a/develop-docs/sdk/telemetry/attachments/upload.mdx b/develop-docs/sdk/telemetry/attachments/upload.mdx
index 6f3160b106ce99..2f847e92f5ce84 100644
--- a/develop-docs/sdk/telemetry/attachments/upload.mdx
+++ b/develop-docs/sdk/telemetry/attachments/upload.mdx
@@ -114,6 +114,22 @@ This allows the client to upload attachments that are much larger than what the
 
     SDKs **MUST** use this location to attach a [placeholder item](/sdk/telemetry/attachments/#attachment-placeholders) to the event envelope. SDKs **MUST NOT** use the `Location` header from the initial `POST` request, or any intermediate request, because it may not contain all the fields needed to create a valid placeholder.
 
+## Common Error Responses
+
+This table lists some of the errors you might encounter while uploading.
+
+| Status                  | Error Text                                                                               | Solution                                                                                                                      |
+| ----------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| 400 Bad Request         | `Missing X-Decoded-Content-Length header`                                                | Specify the size of the request body before compression.                                                        |
+| 400 Bad Request         | `non-final chunk {chunk_length} is smaller than upload granularity {upload_granularity}` | Use chunks of at least `Upload-Min-Chunk-Size` bytes, in multiples of `Upload-Chunk-Granularity`, except for the final chunk. |
+| 409 Conflict            | `upload offset mismatch (server holds {offset} bytes)`                                   | Make a `HEAD` request to obtain the server's current state.                                                                   |
+| 413 Payload Too Large   | `Chunk of {chunk_length} bytes exceeds the remaining {remaining} bytes`                  | You are trying to upload more than you initially declared with `Upload-Length`. Cap the file or look for bugs in the counting logic. |
+| 413 Payload Too Large   | `length limit exceeded`                                                                  | The request's `Content-Length` exceeds the server's request body size limit. Send smaller chunks.                             |
+| 413 Payload Too Large   | _empty response_                                                                         | Split your file into smaller chunks.                                                                                          |
+| 501 Not Implemented     | `upload error: resumable upload declined`                                                | Send the attachment in an envelope instead, or drop it if it is too large.                                                    |
+| 503 Service Unavailable |                                                                                          | Retry.                                                                                                                        |
+| 504 Gateway Timeout     |                                                                                          | Retry.                                                                                                                        |
+
 ## Compression
 
-The byte sizes in the headers refer to the request body _before_ compression, that is, before applying `Content-Encoding`. This applies to `Upload-Chunk-Granularity`, `Upload-Min-Chunk-Size`, `Upload-Max-Chunk-Size` and `Upload-Offset`. The server interprets `Content-Encoding` on a `PATCH` request as a self-contained transport optimization that only concerns the current request in isolation, not the full upload.
+The byte sizes in the headers refer to the request body _before_ compression, that is, before applying any form of `Content-Encoding`. This applies to `Upload-Chunk-Granularity`, `Upload-Min-Chunk-Size`, `Upload-Max-Chunk-Size` and `Upload-Offset`. The server interprets `Content-Encoding` on a `PATCH` request as a self-contained transport optimization that only concerns the current request in isolation, not the full upload.