Hi Everyone,
I am using firestore as a backend for some of my data (it is a language learning app with millions of records that needed to be uploaded at once, so using the bubble DB was unfeasible).
I have a problem with maintaining fidelity between firestore and the bubble client because of the way that bubble caches API requests when the parameter does not change (an otherwise awesome feature given the WU consumption of API requests).
The general pattern my app follows is to check if a field in firestore exists > if not, send an API request to add it. The next time the user sees that data, the previously missing field should appear. However, it does not, due to the caching, thus triggering my app to rerun the upload of the new data again. This negates the bandwidth savings from the original caching, especially since other APIs would be triggered to generate the data that needs to be uploaded.
I could (possibly) add a Date field to the header of firestore API request, so that it overrides all caching, but I really would only want to break the cache in the specific instance where I know the data has been changed (ideally as a workflow action for instance). Is this at all possible? I would even be open to custom solutions.
Thanks!