PICOF Connector Output to Studio Integration Fails With No File Found
The error The output document of PICOF connector is sent over to Studio Integration. The issue is though PICOF generates the xml file, the studio integration fails to get the file. Studio integration ends with no file found error.
What it means
A PICOF connector generates its output XML successfully, but the downstream Studio integration that is supposed to pick that file up cannot find it, even though the file exists. This usually points to a mismatch between what the PICOF connector calls its output (for example a 'Deliverable Document') and what the launch parameter of the Studio integration expects to receive (for example an 'Output Document').
Troubleshooting
- Compare the exact document type the PICOF connector produces against the document type the Studio integration's launch/input parameter expects to consume.
- Check the Studio integration's launch parameters for both 'Deliverable Document' and 'Output Document' options, and confirm which one actually matches the PICOF output.
- Manually inspect the PICOF run's output attachment to confirm the file is genuinely being produced before assuming the problem is on the Studio side.
⚡ Quick fix
Switch the Studio integration's input parameter to reference the specific document type the PICOF connector is actually generating, then relaunch.
✓ Permanent fix
Standardize on a single, explicitly documented document-type handoff between the PICOF connector and any downstream Studio integration, so the two sides can't drift out of sync again.
Was this helpful?