A topic can declare retention so a consumer that subscribes later reads the producer's newest messages first.
Released on October 8, 2026
- An emitted or contract topic can declare
retention: { latest: N }(up to 1024), so a consumer that subscribes later reads the producer's newest N messages before live updates. - Re-sync a consumer after its producer changes a topic's retention:
peppy node syncreads the policy from the producer and the generated subscription applies it. peppy node inforeports the retention of a topic that retains.