The place where most companies get stuck is in the hand-offs between marketing and creative, where teams create, iterate, approve, review and manage content. 1ac2cb6b-032a-4932-a5d0-615208cb8986.Simply adding budget and headcount won’t solve this growing problem.I really appreciate any help I can get with this. I've also attached the PDFs - the 'TEST' pdf is the one created straight from InDesign, then uploaded via the plug-in, the other is the pdf generated by the plug-in. Of course, we could export to folders and use the plug-in just to upload the PDFs but we do that already (create the PDFs and upload to WF) - the whole point of the plug-in is to streamline that process, but we can't do that unless the PDFs are clean, and they're not when we export/upload via the plug-in. In my testing, I have tried exporting different files from our server and from my local drive, I have tried all the default PDF export presets as well as custom presets, and in every case the PDF exported from the WF plug-in is more than 50% corrupt. I question that response because those were isolated to a single user's files and used standard vendor presets that we have never had problems with before. Workfront Support says it's an InDesign export issue, not a plug-in issue because we recently had a couple of files drop out images and text from print-ready PDFs. See the examples below - the item on the left is the PDF output directly to WF, and the item on the right is output using the exact same settings, output to the desktop, then uploaded as a new proof version using the plug-in: No matter what settings I use, when I export directly to WF, the PDF is corrupt (images/text drops out, text frames duplicate on top of each other, etc.).but when I export a PDF to a local folder, then upload that existing PDF using the WF Plug-in, the PDF is fine. I'm having an impossible time exporting PDFs from InDesign and uploading directly to Workfront using the Adobe Workfront Plug-in.

Workfront adobe integration