Oct 2014
9:46pm, 27 Oct 2014
15,118 posts
|
fetcheveryone
It's possible that the time taken to process the file is longer than the Garmin server is willing to wait for a response - so perhaps it's considering it as a failed upload and trying again. I will keep digging tomorrow.
|
Oct 2014
9:47pm, 27 Oct 2014
5,660 posts
|
The_Saint
Me please
|
Oct 2014
9:49pm, 27 Oct 2014
19,742 posts
|
eL Bee!
Fetch - the (earlier of 2) file that failed to upload on Saturday was a smaller one than Sunday's which came through fine.
|
Oct 2014
6:27am, 28 Oct 2014
13,625 posts
|
Ted
Fetch. At 12:22 this morning the app duplicated all of my training back until 28th Sep, with the exception of a Duathlon on the 28th when I did multi-sport on the watch and it made 3 additional copies of each segment.
|
Oct 2014
9:38am, 28 Oct 2014
15,119 posts
|
fetcheveryone
Ey up
The 'last thirty days' thing is expected behaviour - but I'm not sure about the multi-sport session, and how that would have been sent over / handled.
Unfortunately, I've been saving the incoming files using a timestamp and user ID as a filename, but I should have put microseconds on it too, or come up with another system, because the Garmin system is currently sending 20-30 files over all at the exact same time.
|
Oct 2014
9:38am, 28 Oct 2014
15,120 posts
|
fetcheveryone
...so as a result, I've not been seeing all the data files as sent.
|
Oct 2014
12:27pm, 28 Oct 2014
13,626 posts
|
Ted
It's happened again dude. I can see 2 Fetchpoint timestamps at 11:20 and 11:22, there may be more.
Is there anything I can do at this end? I am deleting the training from my log but, I fear this would be a twice daily exercise.
|
Oct 2014
12:36pm, 28 Oct 2014
15,124 posts
|
fetcheveryone
When the files come in from Garmin, the Fetch server responds with an "okey dokey" - I'm working on the theory that the Garmin server is listening out for a set amount of time, and then getting fed up of waiting. I've sent a bunch of questions to their development team, but they're US-based, so there's a bit of a time delay.
Meanwhile, if you want, you can turn it off - just go to the URL I've sent you, and it'll take you through to the page where you can allow/deny.
|
Oct 2014
12:39pm, 28 Oct 2014
198 posts
|
MzG
The larger run was 8.x miles, I uploaded it with the importer instead (bit I've left both 0.71 cool downs).
|
Oct 2014
12:58pm, 28 Oct 2014
15,125 posts
|
fetcheveryone
Ted - each training entry that arrives from the Garmin server has a unique ID - so I'm now looking at those ID's as they come in, and comparing them against a list of ones that I've already imported. So you might see a bunch of duplicates arrive again, but after *that*, the Fetch server should be wise to any further attempts.
|