Skip to main content

​
What Are Deliveries?

Deliveries are the generated digests sent to you based on your newsletter’s schedule. Each delivery contains curated content from your sources, organized by your defined sections.

​
How Deliveries Work

1

Scheduled Generation

At your configured cadence time, Reduce automatically generates a new delivery.
2

Content Fetching

Reduce fetches new content published since your last delivery from all sources.
3

AI Processing

The AI evaluates all new content against your section prompts and organizes matching content.
4

Delivery Creation

A new delivery is created and sent to your inbox (or made available in the app).
Content Freshness: Reduce only includes content published since the previous delivery. You’ll never see duplicate content across deliveries.

​
Viewing Delivery History

To view past deliveries:
  1. Navigate to your newsletter
  2. Go to the Deliveries tab
  3. Browse the list of past deliveries, sorted by date (newest first)
Each delivery shows:
  • Delivery date/time: When it was generated
  • Content count: Number of items included
  • Status: Whether delivery succeeded or encountered issues

​
Delivery Statuses

​
Sent

The delivery was successfully generated and delivered. Content is available to view.

​
No New Content

No content matching your section prompts was published since the last delivery.
This is common for low-volume sources or very specific prompts. Consider adjusting your cadence or broadening section prompts if this happens frequently.

​
Failed

An error occurred during generation or delivery. Common causes:
  • Source API temporarily unavailable
  • System maintenance
  • Rate limiting from content platforms
If you see repeated failures, check the Reduce status page or contact support.

​
Pending

The delivery is currently being generated. This typically takes 1-3 minutes depending on the number of sources and content volume.

​
What Happens When There’s No New Content?

If no new content matches your sections since the last delivery:
  • You’ll receive a notification (email or in-app) that there’s no new content
  • No delivery digest is generated
  • The next scheduled delivery will check for content from the original last delivery date
Example: 
Last delivery: Monday 9 AM (content from Sun 9 AM - Mon 9 AM)
Tuesday 9 AM: No new content matching sections
Next delivery: Wednesday 9 AM (content from Mon 9 AM - Wed 9 AM)
The “no new content” notification still counts as a delivery attempt. The next delivery will include content since the last attempt, not the last successful delivery.

​
Content Freshness Explained

Reduce tracks the timestamp of your last delivery and only fetches content published after that time.

​
Example Timeline

Newsletter: "AI News Daily"
Cadence: Daily at 8 AM
Sources: 3 YouTube channels, 2 subreddits, 2 X accounts

Monday 8 AM Delivery:
- Includes content from Sunday 8 AM - Monday 8 AM
- YouTube: 2 new videos
- Reddit: 5 top posts
- X: 12 posts

Tuesday 8 AM Delivery:
- Includes content from Monday 8 AM - Tuesday 8 AM
- YouTube: 1 new video (different from Monday's)
- Reddit: 3 top posts (new since Monday)
- X: 8 posts (new since Monday)

No duplicates between Monday and Tuesday deliveries

​
Why This Matters

  • Efficiency: You only see genuinely new content
  • No repeats: Content never appears in multiple deliveries
  • Time-bound: Each delivery represents a specific time window

​
Viewing Delivery Content

Click on any delivery to see:
  • Full digest: All sections with matching content
  • Content details: Titles, descriptions, links, timestamps
  • Source attribution: Which source each piece of content came from
Use the delivery view to evaluate whether your section prompts are working as expected. Refine prompts if content doesn’t match your intent.

​
Delivery Limits

  • Free tier: Delivery history retained for 30 days
  • Pro tier: Unlimited delivery history

​
Troubleshooting

​
Delivery Was Empty

Possible reasons:
  1. No new content published: Your sources haven’t posted since the last delivery
  2. Section prompts too narrow: Content exists but doesn’t match your prompts
  3. Source issues: One or more sources are temporarily unavailable
How to diagnose:
  • Check if sources have published new content on their platforms
  • Review your section prompts - are they too restrictive?
  • Look at the delivery status for error messages

​
Delivery Contains Unexpected Content

If content doesn’t match your expectations:
  1. Review section prompts: The AI interprets prompts literally - refine wording
  2. Check source relevance: A source might be publishing off-topic content
  3. Iterate on prompts: Adjust prompts and wait for the next delivery to test
Good prompt refinement takes 2-3 delivery cycles. Don’t expect perfection immediately.

​
Missing Expected Content

If you know a source published something relevant but it’s not in the delivery:
  1. Check timing: Content may have been published before the last delivery window
  2. Review section prompts: The AI may have filtered it out based on your criteria
  3. Verify source configuration: Ensure the source is still added to your newsletter

​
Example Delivery Scenarios

High-Volume Daily

Newsletter: “Tech Twitter Roundup”Cadence: Daily at 9 AMTypical delivery: 15-25 posts from 5 X accounts, organized into 3 sections (News, Tips, Discussions)

Moderate Weekly

Newsletter: “React Ecosystem Weekly”Cadence: Weekly on Mondays at 8 AMTypical delivery: 8-12 items from YouTube channels, subreddits, and X accounts across 4 sections

Low-Volume Selective

Newsletter: “AI Research Papers”Cadence: Every 3 days at 12 PMTypical delivery: 2-5 papers from ArXiv subreddit and researcher X accounts

​
Next Steps