Is there a chance you have this extract on a very regular schedule (eg every 15 mins), which means it's being skipped because it's still running from a previous extract eg kicked off at 1.00, but still runnning at 1.15 when its scheduled to run again... in which case it skips the 1.15 instance (otherwise there is a danger you'd be in perpetual catch up...?)
Based on a quick google, I found this very old thread from 2013Extract refresh skipped, which is what I've made my assumption from.
I forget the exact number, it may be 5. If there are more than x number of schedules consecutive refresh failures for a given extract, then it goes into suspended mode. If you refresh manually, I believe it will be removed from the suspended status.
2 of 2 people found this helpful
Typically the "skipped" error message indicates the extract has failed more than once. The idea being that after so many unsuccessful attempts, it will no longer tie up resources and simply "skip" trying to do the extract until someone manually corrects the issue.
This forum thread gives quite a bit of background:
One of the Administrative Views is "Background Tasks for Extracts". In the upper left you can filter on the extract name and then change the time period and I'm thinking if you go back far enough you could see where the extract first fails and hovering over the failure the tooltip should reveal the error or you could manually submit the extract with the "Run Now" option and wait to see what error message is revealed.
Thank you, manually refresh it and the super-duper-clear-error-message is understandable now