I ran into this while researching #872
I'm not sure of the scope of the issue yet... whether it's a public form issue, an issue with relationships named "status", or any field named "status".
A quick search in the issues is turning up a number of open issues with fields named "status".
There is a package and shortcode from the original WP.org issue report that can demonstrate it quickly:
Drop the shortcode in a page and visit it, you'll see it choking on the 'status' field.
Is this still happening?
I'm wondering if this has something to do with the alias 'status' set for 'post_status' in PodsAPI::get_wp_object_fields()
Adding a field that has an alias on an object field should be disallowed right now. So if this is on a Post Type, it should warn you and not let it save. Is that not the case?
It very well could be fixed then. I created this issue back when I was troubleshooting other things for 2.1 and I haven't returned to it to investigate more closely.
The breadcrumb trail in this thread should be able to repro the situation to test, however.