Post

14 followers Follow
7
Avatar

Export data stuck

I tried to export a range of data. It has been going for over 12 hours without producing anything. I want to stop it but can't find a way.

speedwalkercreed

Please sign in to leave a comment.

24 comments

1
Avatar

yes, I noticed this too.
I get an error message
[Failed to render "settings_content". See log for details.]

Bart Beerden 1 vote
Comment actions Permalink
0
Avatar

I have the same problem. I started the export 16 hours ago and the page keeps refreshing without a result:

"Generating export from 5/11/12 to 7/31/16... should not take more than a few minutes but feel free to go for a run and come back later."

Should not take more than a few minutes? lol...

Martin T. Zavadil 0 votes
Comment actions Permalink
0
Avatar

I noticed exports from 2015 onwards work, takes more like half a day to get the link, but anything earlier than 2015 ends up with nothing. I'm trying to shorten the period in 2014 for export and see what happens.

Brian Tan 0 votes
Comment actions Permalink
0
Avatar

I'm trying to back up (export) all my data from 2011 on to present day. This is when I made all my routes. I never get anything as an export. What gives?

Tony Casper 0 votes
Comment actions Permalink
0
Avatar

Mine has been going for ~ 4 hours... did you ever get your data? Trying to get data going back to 2010

Alex Hakso 0 votes
Comment actions Permalink
0
Avatar

same problem here, I'm chasing weight data back to 2011. seems that it only transferred over to myfitnesspal from sep 2013 onwards. worst thing is i cant even get my lifetime weight graph to work either so i can;t even get the data manually.

Tim Niedorfer 0 votes
Comment actions Permalink
0
Avatar

same problem here, I'm chasing weight data back to 2011. seems that it only transferred over to myfitnesspal from sep 2013 onwards. worst thing is i cant even get my lifetime weight graph to work either so i can;t even get the data manually.

Tim Niedorfer 0 votes
Comment actions Permalink
1
Avatar

I also get an error message
[Failed to render "settings_content". See log for details

Richard Bosch 1 vote
Comment actions Permalink
1
Avatar

"Generating export from 6/26/17 to 6/26/17... should not take more than a few minutes but feel free to go for a run and come back later."

Should not take more than a few minutes?
I am waiting for one day. Still the same message.

Richard Bosch 1 vote
Comment actions Permalink
3
Avatar

I contacted Runkeeper, and they said the error is fixed. Long story short, IT'S NOT!

 

C'mon RUNKEEPER, get with it! You are making the case for moving to another app/company more likely for everyone who is trying to use your "feature" and not getting success.

Tony Casper 3 votes
Comment actions Permalink
1
Avatar

I also get 

[Failed to render "settings_content". See log for details

Anyone know of viable Runkeeper alternatives?

Rick van den Hof 1 vote
Comment actions Permalink
1
Avatar

Same problem.  Tried to export some data and it just gets stuck.  Never gives me the download button to download the generated export file.  Stupid!  I did find that i could export the runs individually by opening each activitiy but couldn't export a weeks worth of runs in one go.  Annoying! Maybe time to get a garmin and use starva.

Stuart Bennett 1 vote
Comment actions Permalink
1
Avatar

This is just a shame from Runkeeper. Practically, as there is no other mean to get your data, it means that they are taking ownership of our property, as it has been days that this bug has been reported and nothing is done about it. Is it the new ASICS management ? Is it because they have just lost consumer connection ? I am highly disappointed by the lack of respect to us...

Gilles G. 1 vote
Comment actions Permalink
0
Avatar

Having the same issue. [Failed to render "settings_content". See log for details.]

Richard Gustavsson 0 votes
Comment actions Permalink
0
Avatar

I have the same issue -

[Failed to render "settings_content". See log for details.]
 
Is there any response from runkeeper?
 
Otherwise it might make sense now to swith to another platform.
Christian 0 votes
Comment actions Permalink
0
Avatar

I had the same problem just now in Chrome, then I switched to Safari, logged in, and was able to make an export. So maybe this will work for others aswell, YMMV.

Rick van den Hof 0 votes
Comment actions Permalink
0
Avatar

Amazing, you are right.

Chrome NOK

Edge NOK

.... and IE is OK !!!

 

Runkeeper, this is amazing, this does not seem to be complicated to fix...

Gilles G. 0 votes
Comment actions Permalink
0
Avatar

I've had two emails from Runkeeper saying this issue is fixed. It is NOT fixed. Same crap happening again and again.

Tony Casper 0 votes
Comment actions Permalink
0
Avatar

Now it just says [Failed to render "settings_content". See log for details.] when I try to export data, doesn't even start to do anything.

Considering that they still didn't fix it, for more than a year, this bug has no priority whatsoever for the dev team (

Alex Kulakov 0 votes
Comment actions Permalink
0
Avatar

With the refusal of Runkeeper to make this a priority (I just want to back up my data since Runkeeper can't seem to do anything right), it may be time to leave RK and find another fitness app.

Tony Casper 0 votes
Comment actions Permalink
0
Avatar

My workouts go back to June 2009 and, when I tried to export all of my data, I also ran into the problem of the export hanging.

After some trial and error, I discovered that my problem was with November 2014. I only had one workout that month (on the 19th), but if that workout's date was part of the range I set, then the export would never generate.

I was able to create two exports that skipped over the problem date:

"01-Jun-2009 to 18-Nov-2014" 
and
"20-Nov-2014 to 14-Sep-2017" (today's date)

Each of these generated within a minute.

FWIW - my trial and error method: export a year at a time (2017, then 2016, etc) until it got stuck on 2014. Then export a month at a time (Dec 2014, Nov 2014, ...) until it got stuck. Skipped over the problem month and discovered the previous month, and years, all worked.

Jay Cagey 0 votes
Comment actions Permalink