You can use the WakeTimer inside the Timer Action. But I would revise this logic. This means you'll have a process consuming CPU resources all the time...

Hello Ferdinand

Regarding your pooling approach and requirements, Waking up the timer will not get you the 1 second pooling intervals you seek, because the OutSystems Scheduler pooling is 20 seconds interval. This means that your timer will only run once every 20 seconds at most.

As for the pooling approach in general, depending on the load and number of requests, it may cause exaustion of resources (threads, or even ephemeral TCP/IP ports).

If you have no alternative using callback events or requests (like André Vieira referred), then you need to adopt a different approach to the pooling:

1. If the pooling total time lapse is within minutes, you can call the WCF service, and keep pooling for the result in loop with 1 second sleeps, all within the timer.

2. Instead of timers, use BPT Process, and use the Wait with a timeout of CurrDateTime()+1 second, and on the On Close action of the Wait, you pool the phone system. BPT has much shorter pooling intervals in the Scheduler (1.5 seconds). As long as there are threads in the BPT Engine to process the activity, it will execute with a 1.5 seconds interval.

Keep in mind that pooling wiht such short time intervals is not recommended, as it exausts resources, and simle isn't a scalable solution.

Hope this information is helpful.

Cheers

 

Offering some constructive criticism, one thing you could do to avoid polling is having a callback mechanism.

Instead of having the Platform constantly polling for new messages, you can add a web service on the platform which the other system calls whenever a new message / call arrives.

Hope this helps.