A low-frequency polling safety net for Etsy inventory, layered underneath the event-driven refresh (#27). Needed because:
there's no webhook for manual listing edits/restocks on Etsy's side
there's no refund/return event among the four supported order webhooks
webhook delivery isn't guaranteed - Etsy retries for ~10 hours then gives up
Mirrors the precedent in domains/amazon's mock processor, which pairs its LISTEN/NOTIFY push path with a configurable poll fallback for the same reason (see that file's history before implementing this).
Frequency should stay comfortably inside COMPLIANCE.md's 24-hour content-freshness bound - every few hours, not daily. Needs the Etsy API client rate-limiting work (#29) to poll safely across shops within the 10,000-calls/day cap.
A low-frequency polling safety net for Etsy inventory, layered underneath the event-driven refresh (#27). Needed because:
- there's no webhook for manual listing edits/restocks on Etsy's side
- there's no refund/return event among the four supported order webhooks
- webhook delivery isn't guaranteed - Etsy retries for ~10 hours then gives up
Mirrors the precedent in `domains/amazon`'s mock processor, which pairs its LISTEN/NOTIFY push path with a configurable poll fallback for the same reason (see that file's history before implementing this).
Frequency should stay comfortably inside COMPLIANCE.md's 24-hour content-freshness bound - every few hours, not daily. Needs the Etsy API client rate-limiting work (#29) to poll safely across shops within the 10,000-calls/day cap.
angel
added this to the Etsy Integration milestone 2026-08-20 23:30:19 -06:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A low-frequency polling safety net for Etsy inventory, layered underneath the event-driven refresh (#27). Needed because:
Mirrors the precedent in
domains/amazon's mock processor, which pairs its LISTEN/NOTIFY push path with a configurable poll fallback for the same reason (see that file's history before implementing this).Frequency should stay comfortably inside COMPLIANCE.md's 24-hour content-freshness bound - every few hours, not daily. Needs the Etsy API client rate-limiting work (#29) to poll safely across shops within the 10,000-calls/day cap.