Increased "Obsolete output mapping" transformation user errors

Since October 10, 3:00 am UTC we are experiencing higher rate of "Obsolete output mapping" user errors in transformation jobs. This issue is caused by a recent update of the transformation component. We'll be rolling back the release as soon as possible and keep you updated on further events.

UPDATE 8:45 am UTC: We have successfully deployed a previous version and all affected configurations should be working now. 

UPDATE October 13, 6:11 PM UTC: A new version with a fix has been released and deployed.

We apologize for the inconvenience.