you already mentioned in your post. Disable the timers and reactivate when required. 

if you know when you timers need to run again, then you can configure accordingly

@Neha Agarwal Timers property Is multi-tenant can be marked as false to avoid run isolated against each tenant.

 if this is not what you want then I would make some DB level criteria (to make the data not available for timers) so timer can not fetch any data even running normally until it required. This approach purely depends on how the timers are fetching data.

While from service center, I don't think there is a way to disable all the timers at once in multi tenant application.

Hi,

Can you check these post.  It might help you.

https://www.outsystems.com/forums/discussion/83766/activate-deactivate-timer-on-specific-tenant/

https://www.outsystems.com/forums/discussion/75761/deactive-timer-to-all-tenants/

Regards,

Wasimkhan S

Hi Neha,

if your platform is on on-prem, you could stop the scheduler service for a while (this would of course also stop other timers from running)  don't know if that is possible for you ?

alternatively, you could try to edit the scheduler data programatically, but this is error prone if you don't know exactly what you are doing.

Dorine

In addition to what Remco is saying,

if you don't want to develop anything, you could also use this query :

this will block your timer from running on the scheduled time, but also block anybody or any code from waking it, or anyone from using the Run Now facility (the timer even becomes invisible in service center list)

Once you put back to active though, a missed schedule or wake timer that happened while it was inactive, will cause a run.

Dorine

Hi @Neha Agrawal, you can create a Boolean site property then at the start of your timer you can check if the site property is set to true and only then run the logic other wise just end the flow in all your timers.

Thanks
Gitansh Anand

Thank you all. 
Seems that there is no way for us to disable all the timers at once in multi tenant application from Service Center or LifeTime.
The coding route is always but we didn't wanted to go that way.

Posting this on idea channel - https://www.outsystems.com/ideas/14252/play-with-configurations-of-multi-tenant-timers-for-all-tenants-in-one-go/

Thanks, 
Neha 

@Neha Agarwal after knowing community experts advise, we know that we have limitations here as I mentioned 

Thank you for posting the idea. it will be beneficial 

Hi @Neha Agrawal ,

At the moment, it is not easy to stop Timers once they've started. That's why implementing the KillSwitch pattern is highly recommended (similar to what Gitansh suggested). You can refer to this article for a solid walkthrough on using this pattern (look for AbortTimer variable): https://itnext.io/how-to-manage-heavy-timers-in-outsystems-6c954789783e

One extra tip: make your KillSwitch Site Property not multi-tenant. That way, you have a single emergency brake that takes effect across all tenants simultaneously, which is much easier to manage if you need to stop a runaway process globally.
It’s worth noting that while this still involves a bit of manual coding within your Timer logic, it’s considered a best practice to implement it anyway. It gives you much better control over your server resources and prevents you from having to wait for a 20-minute platform timeout.

I hope it helps.