Closed mhkeller closed 8 years ago
This particular recipe is grabbing data from 70 articles btw.
it could have just been an aberration too. no harm in increasing the timeout.
Update: I increased the timeout to six hours: https://github.com/newslynx/newslynx-sc-google-analytics/commit/84ea79ad2178f30eea11cc6b6677d30ffa8a617d
It's pulling in the summary metrics appropriately but the timeseries data is coming back as 0
for both GA and share counts. See https://github.com/newslynx/issue-tracker/issues/536 for more info
From the hidden issue, it suggests that share counts are not coming back as zero. it looks like you're probably pulling that data using sparse=true
. the counts will be zero for periods where they weren't collected since the API will fill in these values when sparse=true
.
Ah right, hmm let me see if this is a spotted tail issue then since this is the visual. I'll close this one since it seems increasing the timeout has fixed this issue.
Fyi, resolved through https://github.com/newslynx/newslynx-app/commit/7b234a03361a44c4b0e6b8839efc6ca1f07edffb, which was a string that changed in 1.2.0 and I didn't catch all appearances.
Given how slow GA can be, perhaps we increase the timeout for this or there's something else going on. What do you think @abelsonlive