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 integration seems to be missing rows for at the very least open and receive metrics.
When querying the Klaviyo API manually, the rows can be found. When running with the tap, it is unclear whether the rows have failed to be found, or have failed to upload to the destination, failing to raise an error.
It seems like the tap would use this method to grab data from each metric:
select count(*)
from klaviyo.receive
where _sdc_received_at = <a time>
yields 116 rows.
Logs from the extraction say that 122 rows were extracted and delivered to the destination.
Expected Behavior: 122 rows should have that _sdc_received_at column. Rows that surface when querying the Klaviyo API for that time period should exist in the warehouse.
Tried Diagnostics:
query the Klaviyo API for data with the same start and end time as the failing extraction, using the same syntax outlined in the above hyperlink. Yields all (correct amount) of data.
The text was updated successfully, but these errors were encountered:
The integration seems to be missing rows for at the very least open and receive metrics.
When querying the Klaviyo API manually, the rows can be found. When running with the tap, it is unclear whether the rows have failed to be found, or have failed to upload to the destination, failing to raise an error.
It seems like the tap would use this method to grab data from each metric:
tap-klaviyo/tap_klaviyo/utils.py
Line 150 in 145c9a9
Background:
Example:
running:
yields 116 rows.
Logs from the extraction say that 122 rows were extracted and delivered to the destination.
Expected Behavior: 122 rows should have that _sdc_received_at column. Rows that surface when querying the Klaviyo API for that time period should exist in the warehouse.
Tried Diagnostics:
The text was updated successfully, but these errors were encountered: