I hit the same issue. I went back to retest and now I'm hitting the issue on the test database, where I didn't hit it before...

I'm trying to track down if anyone else knows about this. I can't find anything so far. I think we're going to have to open an issue on Connect. I just did a few searches there. There doesn't seem to be anything. This is either a bug, or we're missing something. I'm just confused by how I got it to work before.