Sometimes a timer runs indefinetly without being processing anything. 


This happens specially if there is an active debug session or a debug session was active some seconds ago.


How to overcome this and stop the timer before the execution timeout?


Thanks in advance

Hi Nuno,

I never encountered this problem.
Could you specify your platform and Service Studio version and stack?

Also, you can consistently reproduce this or is something completely aleatory?

Cheers.

Thanks Eduardo.


Its a problem that i cannot reproduce 100%. But the pattern seems to be the debug session.


Its cloud based.

Development purpose
Debug Mode
Version 11.0.210.0


Eduardo Jauch wrote:

Hi Nuno,

I never encountered this problem.
Could you specify your platform and Service Studio version and stack?

Also, you can consistently reproduce this or is something completely aleatory?

Cheers.



If you are debugging the timer, and you hit a breakpoint, obviously the timer stops executing. If you don't do anything, the timer will time-out. Could it be other people also have opened the same eSpace with debugging?

Thanks Kilian.


If you are debugging the timer, and you hit a breakpoint, obviously the timer stops executing. 


Yes, but after hitting continue the timer should continue, right?


Kilian Hekhuis wrote:

If you are debugging the timer, and you hit a breakpoint, obviously the timer stops executing. If you don't do anything, the timer will time-out. Could it be other people also have opened the same eSpace with debugging?



Only if you use one of the "continue" buttons. Otherwise it will just wait until time-out. It happend with us as well, someone had the eSpace opened and inadvertently pressed "Debug", and we all wondered why the timer didn't do anything :).

Ok, will check that.


Thanks Kilian

Just to add, 

You have the application in the "public" area and the application in the "personal" area of the environment.
If you press F5 (1-click publish), you create a new version of the module in the "public" area. If you press F6 you publish (replace) your version of the app in the "personal" area.

Any Service Studio user with active breakpoints in the module, debugging in the "public" area, will stop on any request to that action.

As Timers can't be debugged in the personal area, you need to agree with your colleagues how and when to debug, as to avoid testing problems.

Cheers.

Thanks Eduardo

Eduardo Jauch wrote:

Just to add, 

You have the application in the "public" area and the application in the "personal" area of the environment.
If you press F5 (1-click publish), you create a new version of the module in the "public" area. If you press F6 you publish (replace) your version of the app in the "personal" area.

Any Service Studio user with active breakpoints in the module, debugging in the "public" area, will stop on any request to that action.

As Timers can't be debugged in the personal area, you need to agree with your colleagues how and when to debug, as to avoid testing problems.

Cheers.