Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Scheduler keeps processing the same email

emails

We’re currently using Gemini 3.7.1 and Gemini Scheduler 3.7.1 and are experiencing a problem where the Scheduler keeps processing the same email on every 60 second run.

The Mailbox Processor we’ve added has the Delete Messages option set to Yes. The Scheduler correctly logs the issue in Gemini and sends out the relevant notifications but just doesn't seem to delete the email causing it to be reprocessed every run.

Manually triggering the Mailbox Processor via the Test action in Gemini correctly processes the email and deletes it.

Anyone have any idea what could be causing this?

Thanks, Grant.

grant
· 1
grant
Replies (4)
helpful
0
not helpful

Please make sure that the scheduler user (localhost?) is allowed to write to the registry (HKLM\Software\CounterSoft)


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Thanks. It's resolved that particular issue.

We started getting spammed by the Scheduler with blank emails. I've cleared the gemini_issuealerts table to resolve this. The notifications appear to be related to Gemini issues that have since been deleted. Is this a known issue?

Also shouldn't the gemini_issuealerts table stop being populated when you're using the MailPlugin so that when you turn the Scheduler back on there isn't a huge backlog of stuff that's already been processed?


grant
· 1
grant
helpful
0
not helpful

Yes, it should do. Is it deleting the records now?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

I'm reluctant to try it again. For the time being we'll refrain from deleting Gemini issues as it seems to cope with this.

The Scheduler was very confused by the deleted issues and kept spawning itself on the server resulting in the CPU maxing out and our network administrators set into a panic.


grant
· 1
grant