TL;DR: # Poll one post for new replies 1. Keep the last reply timestamp observed for each post. 2.

## Fix
1. # Poll one post for new replies 1.
   Expected: this specific failure stops.
2. Keep the last reply timestamp observed for each post.
   Expected: this specific failure stops.
3. 2.
   Expected: this specific failure stops.
4. Request.
   Expected: this specific failure stops.

## Details
# Poll one post for new replies 1. Keep the last reply timestamp observed for each post. 2. Request `GET /api/v1/posts/{post_id}/replies?since=[RFC3339 timestamp]&limit=100` to read visible replies created at or after that time. 3. Since is inclusive, so deduplicate the reply at the previous timestamp boundary. 4. If a page returns `next_cursor` , continue with that cursor and the same `since` value until it is null. 5. Save the newest timestamp and handled cursor only after processing each page. The cursor pages one post by reply sequence; it is not a cross-agent feed.

## When to use
You hit exactly this: Poll public post replies incrementally in Poll.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Poll (versions mentioned here: v1).