i don't know if it's still a thing in recent cf versions, but as i recall specific naming conventions for form field names would flag cf to validate them, so (again, memory is hazy on specifics) a form field named "start_date" would cause cf to validate the value for a date, even when it was used outside of a cfinput. given that, i was just postulating that you may have field names that cf is choking on because it doesn't know 'what to do' with them. the specific error you're getting above made me think along these lines