Hello Team,
Can anyone help me to figure out this issue!
I have a timer in production, but it was not scheduled but it was activated. We need to run it manually from the service center. When I click manually from the service center, the timer will not start executing.
Is the problem occurring due to without scheduling? or Is it work when triggering from the service center?
Thanks in Advance
Hi Sonali Murugan,
have you checked the service center logs?
have you find any message under timer section under monitor tab?
I hope you tested the same timer in dev and qa as well? just to make sure it's working on other environment.
please check the below link as well:
https://success.outsystems.com/Documentation/11/Developing_an_Application/Use_Timers/Monitor_Timers
Thanks,
Manish Jawla
Hello Manish,
Thanks for the response,
It was working as expected in dev and Qa, the problem we had was only on production. We have added a log as well to find out the issue. But the log also not captured.
Is that problem occurring that we are not scheduling it or it will work if we trigger it manually from the service center?
Hi Sonali,
Yes, you have to trigger it manually from service center. Since it is not scheduled.
Hope this helps.
Regards,
The Timer should get executed once it finds an idle thread when you click on Run Now, even when no Scheduling was defined for it.
In addition to the Timer Log reference provided by Manish, please refer to the Monitoring Execution Of Timers and Checking Timer Health section from the below OutSystems Documentation to get more insights:
https://success.outsystems.com/Documentation/11/Reference/OutSystems_Language/Processes/Timer
If you have access to the DB, then can query the respective system tables to understand as well (do this with caution and only for read only purpose). Do check if the Scheduler Service is running on the Production environment, and no runtime exceptions are throw by viewing the Timer Log.
Saurabh
Thanks for your prompt response,
When we manually trigger it from dev and QA it works. But when we manually trigger it in production it doesn't run!
Ideally it should run, but since it's production i would advice you to raise a support ticket to unblock you quickly because you are not even able to see any logs in Monitor section.
Hello Saurabh,
PFA, for the timer log. When I trigger it manually.
By looking at log, it looks like timer executed for 0 sec, there must be some setting or code written in the logic which might be responsible for execution of timer, can you please double check those pre-requisite like table empty condition or some value must be present on db to perform the execution, and compare that with your qa and dev condition then you might get answer why your timer is not executing.
The Timer is running and due to some logic not being satisfied is ending / getting terminated quickly.
You can analyse the code in the Timer, look at the existing logs and monitoring section from Service Center to identify the root cause. If still unable to identify the root cause, then as last resort, will ask you to put explicit LogMessages inside certain areas of the Timer Logic.
Do note that if you are using LogMessage action from System action, then kindly refer to the below documentation to understand how to use it and to verify that its enabled for the Prod instance:
https://success.outsystems.com/Documentation/11/Developing_an_Application/Troubleshooting_Applications/Log_Information_in_Action_Flows