Good question - In theory the frequency depends on the factor of how frequently other teams are introducing breaking changes in terms of API. If the dependency

Good question - In theory the frequency depends on the factor of how frequently other teams are introducing breaking changes in terms of API. If the dependency is too early in development phase and API is changing a lot, then probably that api should not be consumed (internally we don't allow such api to hit prod). But still its a good practice to update snapshots (like you said for stale/seed data) and I have been part of teams that have daily or weekly schedule jobs to run these updates (Both approaches work fine).