Timers being triggered twice.

dimitris-tavlikos · April 27, 2016, 2:42pm

I have setup 3 timers for my app, which are being triggered hourly, each one 5 minutes apart.

I’ve noticed that all 3 of them are being triggered twice. I read somewhere in the support topics that this problem was occurring when the “Run” button was clicked. I did actually tried to test my timers by explicitly clicking the Run button on all of them, but they are being executed twice, even after I completely removed them and creating new ones.

My app ID: 928C4E25-D6F5-22CC-FFD5-0C53BA81D000

Thanks,

Dimitris

kate-maksimenko · April 27, 2016, 3:13pm

Hi!

thank you for reporting. we will try to reproduce this issue.

kate-maksimenko · April 28, 2016, 9:18am

You run timers in debug or in production mode?

dimitris-tavlikos · April 28, 2016, 9:19am

Hello,

In production mode.

Edit: Today they seem to be working OK.

dimitris-tavlikos · April 29, 2016, 7:25am

The behaviour is weird. At some times of day the timers are being called normally, at other times they are being called twice.

An example from the logs:

Please note that I have not changed anything since I posted the issue here.

oleg-vyalyh · April 29, 2016, 11:03am

Hi, Dimitris.
We already know about this problem and working on it.
Thanks for your patience.

dimitris-tavlikos · April 29, 2016, 11:32am

Not sure if it would help, but I am having the same issue in another app: 284099AA-17DC-EA4F-FFE8-CD080BAC8E00

Two timers, one every 61 seconds and the other one every 15 minutes. By the way, I find these to stop working from time to time and having to remove them and re-upload them.

Thanks.

mark-piller · April 30, 2016, 2:56am

Hi Dimitris,

There was an update of the production servers today with a fix for timers. Could you please check if the problem is still happening for you?

Regards,
Mark

dimitris-tavlikos · April 30, 2016, 6:23am

Thank you Mark.

Please allow me a couple of days for this, so that I check how it’s going.

dimitris-tavlikos · May 1, 2016, 5:35pm

Hello, the problem still remains. Right after your update it seemed to be working ok.

Now, all timers in both apps are being triggered twice:

2016-05-01 17:29:03,712 | com.backendless.dxalert.timers.GetLatestSpotsTimer | INFO | Started GetLatestSpotsTimer // Started OK

2016-05-01 17:29:05,728 | com.backendless.dxalert.timers.GetLatestSpotsTimer | INFO | Total time: 2.083883595 seconds. // Finished OK

2016-05-01 17:30:04,259 | com.backendless.dxalert.timers.GetLatestSpotsTimer | INFO | Started GetLatestSpotsTimer // Started OK

2016-05-01 17:30:04,492 | com.backendless.dxalert.timers.GetLatestSpotsTimer | INFO | Started GetLatestSpotsTimer // 2nd start

2016-05-01 17:30:06,864 | com.backendless.dxalert.timers.GetLatestSpotsTimer | INFO | Total time: 2.258019986 seconds. // Finished OK

2016-05-01 17:30:06,260 | com.backendless.dxalert.timers.GetLatestSpotsTimer | INFO | Total time: 1.801170022 seconds. // Finished 2nd

mark-piller · May 1, 2016, 7:10pm

I reopened the internal ticket, set it as blocker and will personally stay on top of this.

anatolii-stepaniuk · May 4, 2016, 9:03am

Hi, Dimitris

Can you share the code of your timers? Either here or on support@backendless.com
Thanks

dimitris-tavlikos · May 5, 2016, 6:29am

I’ve just sent the timers of app ID 284099AA-17DC-EA4F-FFE8-CD080BAC8E00. Thanks.

dimitris-tavlikos · May 5, 2016, 6:33am

Just checked and the timers of this app are being triggered three times:

anatolii-stepaniuk · May 5, 2016, 8:29am

Thanks Dimitris!

We are working on solving this problem.

dimitris-tavlikos · May 7, 2016, 5:30pm

Any news with this? The timers are not being triggered at all since at least yesterday…

dimitris-tavlikos · May 7, 2016, 6:30pm

Ok, after removing the timers completely and setting new start date for both of them, re-uploading fixed the issue. For now at least.

Edit 1: Nope. They just triggered once. I really don’t know what to do. The behavior is really weird.

Edit 2: They seem to run OK, it’s the logging that either delays to be written to file, or not being written at all.

dimitris-tavlikos · May 10, 2016, 5:06am

Nothing?

anatolii-stepaniuk · May 10, 2016, 8:59am

Hi, Dimitris.

This is specifically the task we are working on currently. We’ve made progress and will notify you, when the fix will be planned to release. Thanks for your patience and helpfulness.

arthur-dzidzoiev · May 25, 2016, 2:08pm

Hello,
The issue had been fixed, timers were run one time and are set to execute as scheduled.
Please notify us ASAP if you notice some timer misbehaviours.
Best regards,

Artur