How to check all email in one go ?

I am using a job to monitor email, but I noticed it will only pick up one email at a time, then pause for whatever period I configure the job to schedule the checking until it will process the next email. Is there a way to check all emails in one go ?

No. This is done on purpose. The email data is saved to temporary files folder. This way in case multiple emails come with the same message or attachment, the job has a chance to rename attachment files and/or process them before they are overwritten by the next email.

PS This email-watch mechanism in 24x7 Scheduler is designed for using email as a remote job semaphoring/triggering method and for automatic various email-based data feeds, for example data files coming from suppliers, etc…. It is not designed for high volume email processing. For high volume email processing please use 24x7 Event Server.

Thanks for your clarification. Actually yes we are going to use this to capture data file coming from our customer, and I am talking about 40 messages a day but unfortunately they will come within the same hour. Hence if the system can only process 1 email at a time per minute, it will take 40 minutes to process them and does not sound reasonable from our customer perspective.

From the 24x7 scheduler document, which is very comprehensive. What I am thinking to do as a workaround is to create multiple 'identical' job, say 4 jobs schedule to run every minute, hence all these job will start at the same time, making use of the queuing mechanism to process email one at a time. As a result, I can at least process 4 emails per minute and can finish 40 emails in 10 minutes. Downside is I need to make sure all these jobs are identical otherwise it will be very difficult for me to troubleshoot problems.

Do you think this is a reasonable workaround ?

I think your plan should work. If you create them as jobs of script type, for example JAL, you can make them call a user defined statement, in which you can place the business logic code. This way, you can maintain the code in one place and use multiple jobs as multiple triggers for that code.