Cursor expired
type | https://docs.frem.sh/reference/api/errors/cursor-expired |
| HTTP status | 410 Gone |
What it means
The cursor points before the oldest event still kept. The event feed keeps events for 7 days, so some events after your cursor are gone.
Example detail messages returned with this error:
- Events before 1234 are no longer kept (the feed keeps 7 days). Resume from next_cursor, and re-read state you may have missed from the API.
What to do
Resume from the next_cursor in the response body. Events between your old cursor and it are gone, so re-read the state you care about (open pull requests, checks, holds) from the API once.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/cursor-expired",
"title": "Gone",
"status": 410,
"detail": "..."
}Branch on type, not on title or detail - those are human-readable and may be reworded.