Looks like some recent performance enhancements caused this to break. We've pushed a fix to resolve the issue today. Please let us know if you see this issue again.