Bigquery trigger not respecting de-duplication key anymore

Hi,

I am running quite a few BigQuery triggers in my pipedream flows. However, suddenly they’ve all started triggering en mass. It seems to no longer be respecting the de-duplication key. Any idea on how we can prevent this?

I have made no changes, this has been occurring for about 2 days now.

Hi @tom-af6d51,

We’re sorry for your issue! This issue was fixed now.

The reason is that the data store (Redis) that processed deduped events filled up, and Redis starting evicting data. We’ve expanded that db and added better alerts for this case.

Please let us know if you’re still facing the issue. Thanks!