Processing a "Stuck" file

A file may become “stuck” in a source folder if one of the following occurs:
•     A file event is deactivated and then activated while the kernel is running.  When the file event is activated, any files already sitting in the folder are ignored.  Only files created while the file event is running are processed.
•     Adeptia shuts down without a graceful shutdown.

To force a file that is “stuck” in a source folder, there are 2 different procedures you can follow.  Either works equally well; you may want to consider the number of stuck files when choosing which method to use.

Using rename of file(s)
Note:  This method is best if there is only a small number of files to process.
1.     Open the source folder.
2.     For each “stuck” file, rename the file by placing “_1” after the file name but before the suffix.  (For example, you would rename 9Z2.110512105924_06022011015758PM.xml to 9Z2.110512105924_06022011015758PM_1.xml.)
3.     You will see the file process the next time the file event triggers.

Temporarily removing file(s) from source folder:
Note:  This method is best if there are a large number of files to process.
1.     Open the source folder.
2.     Copy all the stuck files to your desktop or some other safe location.
3.     Delete the stuck files from the source folder.
4.     Navigate to Deploy -> Events & Triggers -> File.
5.     Put your cursor on the Name of the file event that uses the source folder and click.
6.     Check the time in the NextFireTime field.
7.     Once that time has passed, copy all the stuck files from your desktop or safe location back to the source folder.
8.     You will see the files process the next time the file event triggers.