Does anyone know the practical limits of how much can or should be stored in a
Continuation? Docs say Continuation is “not designed for persisting large amounts of data between executions.”
- I’m working on a pack for Copper CRM that pulls in Opportunities (some CRMs would call these Deals) via a sync table.
- Each Opportunity can be assigned in Copper to someone on your team, identified in the API response as an
- Coda allows you to have a column try to auto-match to a Coda user based on their email address. So I need to grab a list of assignee_ids and their corresponding email addresses from Copper. Ideally I only do this once, at the beginning of the sync, and then I can match this against any assignee_ids I encounter through multiple continuations.
- My current solution is to store this list of Copper users in the Continuation object (type definition doesn’t allow arrays, so I’m using the slightly janky approach of using the assignee_ids as keys and email addresses as values). I’m not sure what a realistic upper bound is on number of users… a couple dozen? (Any more than that and I’m going to hit all kinds of other limitations like the 10k row limit)
I know I could re-fetch this list with every page of results, but that seems wasteful (unless Coda’s caching means it’s not?). Does this seem like a bad idea?