Problems with document processing

In this section:

1. File not found errors occur when files exist
   This section is not applicable to Windows. If a job goes into an error state and you see File Not Found errors when the files actually do exist, you might need to increase your system setting for the maximum number of open files.
2. Document property values are missing
   If you try to view document property values in the user interface and they do not display, your workflow might not have written the property values to the database yet, or the properties might be defined as limited properties.
3. Document property values are not current
   If you view database property values in the user interface and they are not current, their values might not have been updated in the database using the values in the document properties file.
4. Incorrect documents are attached to emails
   If incorrect documents are attached to emails in the EmailDocuments step, there are a few items you can check to determine the cause of the problem. There is no validation for matching email addresses with attachments.
5. Emails are sent without documents attached
   If emails are sent without documents attached to them, the attachment might not be in the PDF format, the EmailDocuments step might be incorrectly configured, or the PDF might not contain information for each recipient.
6. Problems with list files
   If you set up a workflow to pull documents from jobs before printing or other processing, but experience issues with incorrect documents left in the job or incorrect documents pulled from the job, you might need to update some settings.