Multiple events per transaction

[RohovDmytro]

Hi! I'm seeing multiple runs of a Google Cloud Function created by RevenueCat Extension.

1. RevenueCat Integration creates a Google Cloud function
2. Min instances for it is 0
3. When RevenueCat posts an event it make GCP Function start from cold
4. The start takes too long so someone (RevenueCat?) detects a timeout
5. RevenueCat sends a second request (to already pre-warmed function from the first call)
6. The first request actually was not cancelled, just delayed.
7. THe event from the first request start being processed
8. The event from the second requests start being processed

Thus I have a situation when a single RevenueCat event dispatches two events both of which got handled.

Can we make RevenueCat wait for the cold start longer? Can we set a min instances for a Google Cloud Function through extension settings?

[vicfergar]

Hi @RohovDmytro,

Thanks for the detailed explanation.

It sounds like the issue you’re describing is related to cold starts and duplicate processing of events. However, I would like to understand why this is an issue for you. The extension function should handle this by using unique identifiers (UUIDs) for each event, preventing duplicates when storing events and customers in Firestore Collections.

Regarding the min-instances parameter, you are correct that we haven’t included that parameter in the extension definition yet. However, we can add it if needed. Please note that setting min-instances to a value greater than 0 will result in a monthly fee for the function, as it will keep instances warm even when not in use. For details, see the Pricing page.

If you’re still experiencing problems with duplicate events, could you provide more details on how this is affecting you? This will help us better understand and address the issue.