docs: document scheduled sending with send_at parameter#76
Open
fern-api[bot] wants to merge 1 commit into
Open
docs: document scheduled sending with send_at parameter#76fern-api[bot] wants to merge 1 commit into
fern-api[bot] wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="fern/pages/guides/sending-receiving-email.mdx">
<violation number="1" location="fern/pages/guides/sending-receiving-email.mdx:45">
P2: The Python scheduled-send example uses a timezone-naive `datetime` while documenting UTC, which can schedule at the wrong time if interpreted in local/default timezone. Use an explicitly UTC timestamp.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| subject="Quick question about your garden", | ||
| text="Hi, I wanted to follow up on the seedling order.", | ||
| html="<p>Hi, I wanted to follow up on the seedling order.</p>", | ||
| send_at=datetime(2026, 3, 5, 9, 0, 0), |
Contributor
There was a problem hiding this comment.
P2: The Python scheduled-send example uses a timezone-naive datetime while documenting UTC, which can schedule at the wrong time if interpreted in local/default timezone. Use an explicitly UTC timestamp.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At fern/pages/guides/sending-receiving-email.mdx, line 45:
<comment>The Python scheduled-send example uses a timezone-naive `datetime` while documenting UTC, which can schedule at the wrong time if interpreted in local/default timezone. Use an explicitly UTC timestamp.</comment>
<file context>
@@ -25,6 +25,47 @@ client.inboxes.messages.send(
+ subject="Quick question about your garden",
+ text="Hi, I wanted to follow up on the seedling order.",
+ html="<p>Hi, I wanted to follow up on the seedling order.</p>",
+ send_at=datetime(2026, 3, 5, 9, 0, 0),
+)
+
</file context>
Suggested change
| send_at=datetime(2026, 3, 5, 9, 0, 0), | |
| send_at=datetime.fromisoformat("2026-03-05T09:00:00+00:00"), |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a "Scheduled sending" section to the Sending & Receiving Email guide, documenting how to use the send_at parameter when creating a Draft to schedule emails for future delivery.
Summary by cubic
Add a “Scheduled sending” section to the Sending & Receiving Email guide, showing how to schedule emails by setting the send_at parameter on Drafts. Includes Python/TypeScript examples, status tracking via send_status, and steps to cancel or reschedule.
Written for commit c996ebb. Summary will update on new commits.