1. AuraPlayer
  2. FAQ/ How-To
  3. Admin

Articles in this section

See more

MailListener: ServiceManager doesn't handle my email message Follow

Mail listenening and RPA processing stragegy

Mail listening strategy

  1. Upon establishing a sucessful connection for the first time, the ServiceManager will fetch and process all read/unread* emails found in the inbox, by order of receival date.
  2. In parallel, it'll start listening to any new emails.
  3. For every new email:
    1. We'll skip emails in which the listener is mentioned as CC/BCC/NEWSGROUP**.
    2. We'll match the email to any matching triggers, and add it to a queue for processing (see Rpa processing queue below).
    3. The email will be marked as read (regardless if it matches or not).
    4. If the email matched to any trigger, it'll be moved to the completed folder***.

* Until 2023-05, the ServiceManager was only processing Unread emails in the inbox.
** Unless RPA_MAIL_TRIGGER_HANDLE_CC_BCC is turned on in the System Properties.
*** IMAP_COMPLETED_FOLDER, or if not configured then it'll remain in the inbox.

 

Rpa processing queue

This queue (one queue for any RPAs altogether) holds tasks of {email,rpa} and moderates RPA execution.
It is limited by RPA_MAIL_EXECUTOR_CORE_POOL_SIZE and RPA_MAIL_EXECUTOR_MAX_POOL_SIZE.

Any available executor thread will pull a {email,rpa} task from the queue, and execute the rpa.

You may monitor the number of tasks in queue in Admin->Threads->Email RPA queue (above the table).

 

 

 

Checklist: why my email message not being handled?

1) Check the Mail Listener Status in Admin->Mail (see "Connection status" here).

If it's not connected, reconnect it by clicking "Save". 
 

2) Check the Mail Listener Log (more info in "Logging: monitoring receival of emails" here).
     If you have multiple listeners, it is advised to filter the log by listener. 

    If the log shows that your message was queued, it means that the message was received, matched a trigger, and you should continue by looking for the rpa's execution in Statistics screen or the Main log.

 

3) Other error messages the Mail Listener log may show, and their meaning:

Log message Meaning Solution
KeepAliveThread: terminating since reconnect failed The listener got disconnected and tried reconnecting multiple times but failed - it won't try again.

Check your settings by going the Admin->Mail->(your listener)->Test settings.

Decrease IMAP_MAIL_LISTENER_NOOP_FREQUENCY_MIN.

Manually retart the listener by Admin->Mail->Save.
KeepAliveThread: ended wait for IdleThread [state=RUNNABLE] - periodical reconnect The listener periodically reconnects, to indicate to Google/Microsoft that it's still alive. Normal behaviour, no action needed.
...: message is skipped since the listener is addressed as a CC/BCC/newsgroup recipient By default, mail messages must have the listener's email address listed as "To".
 		 Resend the email, with the listener as "To".

You may turn off this validation and allow CC/BCC/NEWSGROUP by setting RPA_MAIL_TRIGGER_HANDLE_CC_BCC=true in Admin->System Properties.
It is also a valid workaround for email Alias.
MailReceiver: Ignored Message [...] - message doesn't match any handlers The message didn't meet the criteria of any of your triggers.

Open the trigger you indended to run, and compare every filter vesus your mail message.

Switch the following System Properties to TRACE, and re-send the email, so a more detailed reason will be logged:

log4j.rootLogger=TRACE, H
log4j.logger.mailLogger=TRACE, mailAppender
MailReceiver: '...' folder is unavailable, handled emails will remain in Inbox The mail folder to which we move emails after reading them doesn't exist or mispelled.

Check IMAP_COMPLETED_FOLDER setting in Admin->System Properties.

Search the Mail Listener log for "MailReceiver: folders are ..." to see which folder names your account has. 
Other errors   Contact the AuraPlayer team

 

 

Comments

0 comments

Please sign in to leave a comment.