I have a timer with a task that executes in about 2.5 sec to 3.5 sec.
Operations in the task are fixed and don’t change. In fact, almost never in 4 secs.
In practice, I have encountered, out of the blue a rare 5 sec timeouts that occur (as I am in Cloud 9 plan).
This causes my timer to re-run the task and I end up with a duplicate. Is there a way, I can handle a timeout scenario using Codeless, so that I am aware of it and can address the issue.
As of now, this skips my attention, the task gets executed twice and I am aware of it only when client intimates me about it.
Any pointers will help.
Divide your operation into subtasks and add logging so you can see at which step problems occur.
Thank you for the reply @Inna_Shkolnaya.
Like I said, it happens really rarely.
Even if there is no way for me to handle it, can I at least get intimated of a timeout error so that I can address it sooner than what I am currently doing. (only when client intimates).
At this moment we do not have a developer notifications system.
After a quick brainstorm, I can suggest you the following approach:
- then you run your timer code
- now create a new timer which can run as frequently as you need to get notifications, for instance (once a minute)
What do you think?