I'm not sure why this is only triggering now, though. It sounds like a more general issue with the way the json gets written.