James,

To add more information on this issue, this happens in new phoenix views associated with brand new tables as well. So, this cannot be an upgrade/migration issue. Not figured out a specific way to reproduce this issue yet. Could you throw some ideas on what direction this problem could be approached from this point?

Thanks,
Arun