Skip to content

docs: document scheduled sending with send_at parameter#76

Open
fern-api[bot] wants to merge 1 commit into
mainfrom
fern/schedule-send-docs
Open

docs: document scheduled sending with send_at parameter#76
fern-api[bot] wants to merge 1 commit into
mainfrom
fern/schedule-send-docs

Conversation

@fern-api
Copy link
Copy Markdown
Contributor

@fern-api fern-api Bot commented Mar 4, 2026

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.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 4, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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),
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"),
Fix with Cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants