billions-terabyte-89990
03/15/2021, 5:34 AMbillions-terabyte-89990
03/15/2021, 5:45 AMbillions-terabyte-89990
03/15/2021, 8:32 AMfew-river-57214
03/15/2021, 9:27 AMbillions-terabyte-89990
03/15/2021, 7:28 PMdocker run [image_name]:latest npm test
?adorable-tailor-26081
03/16/2021, 12:51 AMbillions-terabyte-89990
03/16/2021, 3:56 AMintegrations
being used to pass data, is that a way to pass data to destinations that that don't fit well in other places, or would be NA in other contexts? Docs make it sound like it's just a boolean for enable/disablerhythmic-pizza-93292
03/16/2021, 1:24 PMfew-byte-85764
03/17/2021, 3:38 PMambitious-journalist-66344
03/17/2021, 8:52 PMFailed to fetch AWS region for bucket
.fast-agent-4711
03/18/2021, 5:16 PMcold-rose-44557
03/19/2021, 1:22 AMTest Connection
I get the following errorcold-rose-44557
03/19/2021, 1:22 AMcold-rose-44557
03/19/2021, 1:23 AMstocky-house-79399
03/19/2021, 1:19 PMexporting_data_failed
error from our live events view for our destination (redshift):
"{\"exporting_data_failed\": {\"errors\": [\"2 errors occurred:\\n1 errors occurred:\\nSkipping users table because it previously failed to load in an earlier job: 12941\\n2 errors occurred:\\npq: 1023\\npq: 1023\"], \"attempt\": 14}}"
Note: The actual error payload is pretty large, but it’s the same message repeated over.
Only our users
and identifies
tables show up as failed. All other tables seem to be uploading correctly.stocky-house-79399
03/19/2021, 1:20 PMworried-match-96789
03/22/2021, 2:28 PMhundreds-lifeguard-65770
03/22/2021, 2:29 PMripe-kite-57109
03/22/2021, 4:54 PMcold-rose-44557
03/22/2021, 7:25 PMgorgeous-planet-70689
03/23/2021, 3:18 AMcold-rose-44557
03/23/2021, 7:59 AMcertificate is valid for *.<http://us-west-2.snowflakecomputing.com|us-west-2.snowflakecomputing.com>,
*.<http://snowflakecomputing.com|snowflakecomputing.com>, *.<http://global.snowflakecomputing.com|global.snowflakecomputing.com>, *.<http://prod1.us-west-2.aws.snowflakecomputing.com|prod1.us-west-2.aws.snowflakecomputing.com>,
*.<http://prod2.us-west-2.aws.snowflakecomputing.com|prod2.us-west-2.aws.snowflakecomputing.com>,
*.<http://us-west-2.aws.snowflakecomputing.com|us-west-2.aws.snowflakecomputing.com>,
not <http://ez35870.ca-central-1.snowflakecomputing.com|ez35870.ca-central-1.snowflakecomputing.com>)\", \
dazzling-wolf-32714
03/23/2021, 5:23 PMdazzling-wolf-32714
03/23/2021, 5:24 PMdazzling-wolf-32714
03/23/2021, 5:24 PMvictorious-wire-44732
03/23/2021, 5:28 PMvictorious-wire-44732
03/23/2021, 5:31 PMvictorious-wire-44732
03/23/2021, 5:31 PMvictorious-wire-44732
03/23/2021, 6:16 PMuseAutoTracking
off, the page bug doesn't occur. I can manually call rudderanalytics.page(null, null { path: r.pathname }) to trigger a page event with the right path propertyvictorious-wire-44732
03/23/2021, 6:16 PM