You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current method of allowing a user to configure adaptive survey response collection depends on a celery task that runs once every 12 hours to see if we've reached the allowed number of responses for the day.
This method doesn't guarantee that we stay under the limit of allowed responses as the response collection happens in the ingestion pipeline and there's no enforcement of any daily limits there.
The alternative here is :
In posthog-js SDK, query the adaptive limits & responses received for the day and only show the survey if the responses_receveid < allowed_limit
In the ingestion pipeline, discard the survey response if the survey received limit is reached for the day
#2 above is destructive and can cause customers to be confused about why they sent a survey response in, and it never showed up.
#1 is ideal in this case, since we can just hide the survey as we do with other feature flag check failures and the survey can be shown the next time the user visits the page.
The text was updated successfully, but these errors were encountered:
Problem Description
The current method of allowing a user to configure adaptive survey response collection depends on a celery task that runs once every 12 hours to see if we've reached the allowed number of responses for the day.
This method doesn't guarantee that we stay under the limit of allowed responses as the response collection happens in the ingestion pipeline and there's no enforcement of any daily limits there.
The alternative here is :
#2 above is destructive and can cause customers to be confused about why they sent a survey response in, and it never showed up.
#1 is ideal in this case, since we can just hide the survey as we do with other feature flag check failures and the survey can be shown the next time the user visits the page.
The text was updated successfully, but these errors were encountered: