Comment 6 for bug 1448783

After some investigation over the weekend, I *think* this is being caused by the twitter scope crashing in certain situations (for me it was with a slow network). I've fixed the twitter scope to simply fail gracefully rather than crash and potentially take stuff down with it, hopefully that will solve the issue. Have also set ResultTtlType as mentioned in another bug, this should cause the scope to refresh automatically, thereby making sure the date is correct