Dbms_scheduler.file_watch will only pull in files with t/s = last run...

Question

Hello,
I may be missing something easy, but instead of spinning my wheels I'll ask.
I am new to using the file_watcher in the dbms_scheduler so I followed the directions posted in this link:
http://awads.net/wp/2011/03/29/did-you-know-about-file-watchers/
Now this works, I can process the file.
But the file_watcher WILL ONLY Pull files that are modified/created AFTER the last run.
Since I am NOT running this in parallel, that means any file not picked up in the initial run will simply sit out there aging.
Am I missing something? I understand that it may be desired behavior to only pick up new files, but our process moves the files out of the directory once they are found. It seems odd that if you do not run it in parallel the file will be ignored forever more.
Am I missing a param?
--Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
BEGIN
      DBMS_SCHEDULER.create_program (
         program_name          => 'FILE_INGEST',
         program_type          => 'STORED_PROCEDURE',
         program_action        => 'Package.Procedure',
         number_of_arguments   => 1,
         enabled               => FALSE);
      DBMS_SCHEDULER.define_metadata_argument (
         program_name         => 'FILE_INGEST',
         metadata_attribute   => 'event_message',
         argument_position    => 1);
      DBMS_SCHEDULER.enable ('FILE_INGEST');
      DBMS_SCHEDULER.create_file_watcher (
         file_watcher_name   => 'watcher_fw',
         directory_path      => '/mydiriwanttowatch',
         file_name           => '*',
         credential_name     => 'sys.cred' ,
         destination         => NULL,
         enabled             => FALSE );
      DBMS_SCHEDULER.create_job (
         job_name          => 'FILE_INGEST_WATCHER',
         program_name      => 'FILE_INGEST',
         queue_spec        => 'watcher_fw',
         auto_drop         => FALSE,
         enabled           => FALSE);
    DBMS_SCHEDULER.enable ('watcher_fw,FILE_INGEST_WATCHER');
END;
/

Answer 1

okay,
Lets say the time of the last run is
05/12/2011 @18:00pm
I place three files into the directory
File1 05/12/2011 18:01
File2 05/12/2011 18:02
File3 05/12/2011 18:03
At the 18:10 run, file1 is picked up and processed
File2 and File3 never get processed or sent to the stored procedure to run (even on the 18:20, 18:30 etc file_watcher runs). however, if I go into file2 and make a change (at 18:35) the 18:40 run will pick it up...
but without manual intervention File3 will never get sent to the stored procedure.
I would expect, at the minimum, that on the first file_watcher job that ran file1 would be picked up, then file2 and file3 and the next subsequent runs (without manipulation).
what I mean about not running in Parallel:
DBMS_SCHEDULER.set_attribute('FILE_INGEST_WATCHER','parallel_instances',FALSE);Edited by: Harrison on May 12, 2011 3:11 PM