Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


argentiere
2015-05-14T10:22:22Z
Since the last update, we have noticed that jobs triggered by emails are activating twice. The email trigger is set to move the email into a sub-folder so it won't find it in the Inbox. Before the latest version we had no problems.
Sponsor
Forum information
Support
2015-05-14T11:49:40Z
Enable Extended debugging (Settings tab->Log->Extended debugging). Look closely in the log_serverDATE.txt when a new email arrives. Maybe you have several Triggers or something else happens. If you cannot figure this out then please send log_serverDATE.txt to support@visualcron.com. Let us know which time the email arrived and the related Job name.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
twagner
2015-05-14T13:59:50Z
We are experiencing the same thing since updating to 7.64.
Support
2015-05-14T15:56:03Z
Could you please post some screenshots of your settings in the Email Trigger?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2015-05-14T16:47:38Z
Which version did you upgrade from? There is no change since 7.5.0. We tried to reproduce it with latest but could not.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2015-05-14T17:06:23Z
Should not be a difference but please test with 7.6.6: http://www.visualcron.co....aspx?g=posts&t=4940 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
argentiere
2015-05-15T07:20:36Z
Support
2015-05-15T07:30:18Z
Thanks, please send the Job name and the file log_serverDATE.txt to support@visualcron.com
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
argentiere
2015-05-19T09:18:41Z
We have found a work around.

Originally we specified that the email would be deleted and copied to a sub folder.

After we changed this to mark as read only and not move. The problem goes away.

It seems the bug is that the email is not marked as deleted the first time the trigger fires, but the second time it does get moved.
Support
2015-05-19T09:40:20Z
Originally Posted by: argentiere 

We have found a work around.

Originally we specified that the email would be deleted and copied to a sub folder.

After we changed this to mark as read only and not move. The problem goes away.

It seems the bug is that the email is not marked as deleted the first time the trigger fires, but the second time it does get moved.



Ok, in new build we move instead of copy+delete - please try that.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
argentiere
2015-05-19T12:07:27Z
Originally Posted by: Support 

Originally Posted by: argentiere 

We have found a work around.

Originally we specified that the email would be deleted and copied to a sub folder.

After we changed this to mark as read only and not move. The problem goes away.

It seems the bug is that the email is not marked as deleted the first time the trigger fires, but the second time it does get moved.



Ok, in new build we move instead of copy+delete - please try that.



Will it also mark as read. I think the default action on any email trigger (to prevent double triggers etc.) is to always mark as read even if not moved.
Support
2015-05-19T12:26:05Z
Originally Posted by: argentiere 

Originally Posted by: Support 

Originally Posted by: argentiere 

We have found a work around.

Originally we specified that the email would be deleted and copied to a sub folder.

After we changed this to mark as read only and not move. The problem goes away.

It seems the bug is that the email is not marked as deleted the first time the trigger fires, but the second time it does get moved.



Ok, in new build we move instead of copy+delete - please try that.



Will it also mark as read. I think the default action on any email trigger (to prevent double triggers etc.) is to always mark as read even if not moved.



We do not Trigger on unread. We trigger on mails we have not seen before. So it does not matter if it marked as read or not.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
jefferyj2
2016-01-07T14:58:36Z
Did you find a fix for this issue? We are facing the same issue in our environment (version 7.6.3).
Support
2016-01-07T19:20:14Z
Originally Posted by: jefferyj2 

Did you find a fix for this issue? We are facing the same issue in our environment (version 7.6.3).



Is it still firing twice after restarting the VC service?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top