Common issues and setup errors
These are the common issues and errors that you might encounter when you are setting up an IMS File Processing Task:
- Underscores in object name: Your IMS objects might have an underscore in their names. Use only alphanumeric values.
- Ensure that the documentName in the message exactly matches the IMS Document Name configured in WFM. To check the correct filename, go to .
- Missing Variation ID: If your Variation ID is missing, duplicated file names may cause errors or overwrite issues.
- When you use the IMS File Processing Task feature, files are stored in the SCHEDULER_IMPORT area of the file storage in WFM. The underlying storage depends on your deployment type. For cloud or multi-tenant deployments, it resolves to S3. For single-tenant or on-premise deployments, it resolves to a local or container filesystem.
- No visible file despite Stored document status: The document status shows that the document is stored but there are no visible files. This status indicates that the document was processed, but the Job Scheduler configuration is incorrect. For example, an incorrect destination path was specified.
- UTC Process Date is null: This indicates that the task was not run or failed silently. You must check the Job Scheduler logs.