Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(messaging): say a status 404 right after a send means queued (#130683)

Michael Reichenbach802ddeb34a35
diff --git a/products/messaging/backend/presentation/views/transactional_email_status.py b/products/messaging/backend/presentation/views/transactional_email_status.py
index f3deae2c53b5..550fee6233f5 100644
--- a/products/messaging/backend/presentation/views/transactional_email_status.py
+++ b/products/messaging/backend/presentation/views/transactional_email_status.py
@@ -101,15 +101,17 @@ class MessagingEmailsViewSet(TeamAndOrgViewSetMixin, viewsets.ViewSet):
200: EmailStatusSerializer,
401: OpenApiResponse(description="The request has no project secret API key."),
404: OpenApiResponse(
- description="No email of this project has this ID, or it is older than 30 days. A send can also "
- "answer 404 for a few seconds right after it was queued."
+ description="No email of this project has this ID, or it is older than 30 days. In the first "
+ "seconds after a send, it means the email is queued but its first status isn't recorded yet."
),
},
summary="Get a transactional email's status",
description=(
"Get the status of one transactional email by the `message_id` that the send returned, for 30 days after "
"the send. Needs a project secret API key with the `transactional_email:read` scope. A key with "
- "`hog_flow:read` also works, but that scope reaches the rest of Workflows too."
+ "`hog_flow:read` also works, but that scope reaches the rest of Workflows too. The first status is "
+ "recorded a few seconds after the send, so a read right after a send can answer 404. Treat that 404 as "
+ "`queued` and read again a few seconds later."
),
)
def retrieve(self, request: Request, *args: Any, pk: str | None = None, **kwargs: Any) -> Response:
diff --git a/products/messaging/frontend/generated/api.ts b/products/messaging/frontend/generated/api.ts
index 15e37e6f5169..25f56be7d99e 100644
--- a/products/messaging/frontend/generated/api.ts
+++ b/products/messaging/frontend/generated/api.ts
@@ -81,7 +81,7 @@ export const getMessagingEmailsRetrieveUrl = (projectId: string, id: string) =>
}
/**
- * Get the status of one transactional email by the `message_id` that the send returned, for 30 days after the send. Needs a project secret API key with the `transactional_email:read` scope. A key with `hog_flow:read` also works, but that scope reaches the rest of Workflows too.
+ * Get the status of one transactional email by the `message_id` that the send returned, for 30 days after the send. Needs a project secret API key with the `transactional_email:read` scope. A key with `hog_flow:read` also works, but that scope reaches the rest of Workflows too. The first status is recorded a few seconds after the send, so a read right after a send can answer 404. Treat that 404 as `queued` and read again a few seconds later.
* @summary Get a transactional email's status
*/
export const messagingEmailsRetrieve = async (