ERROR - Timer reached maximum number of retries (1) [Calculating next run]

Hi guys,

I've been struggling with the following error "Timer reached maximum number of retries (1) [Calculating next run]" when the timer tries to run for the first time in the day. When I "run" the timer manually I have no problems.

What do you guys think might be causing this error?


Thanks.


Hi Samuel,

Normally associated with that error is another error. On service center near that error don't you see another error in the same timer?

Regards,

Marcelo

No, there's no other error being displayed.

Marcelo Ferreira wrote:

Hi Samuel,

Normally associated with that error is another error. On service center near that error don't you see another error in the same timer?

Regards,

Marcelo


Marcelo, I double checked and I found out an other error. 

The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.

What do you think might be closing the connection suddenly?



Hi Samuel,

You need to explain what the timer does so I can understand what can be causing that. From what I remember I already saw that error when connection to an API. Check both this threads

https://www.outsystems.com/forums/discussion/15641/tip-the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-rece/

https://www.outsystems.com/forums/discussion/41263/error-the-underlying-connection-was-closed/

Regards,

Marcelo