Hi Kane,

As Timer runs in different process you will not get the session variable there. instead you can pass the session variable data as input parameter to the timer (if you are triggering the timer from your web app) or you need to store the session variable in DB (if the timer is triggering from a scheduler)  and then you can use it in the aggregate.

Best Regards

Devendra

Hi Kane,

From where you are triggering timer from web app or from scheduler?

Yes we cannot pass the input from web app we can only wake up the timer. better store the session variable in DB from web app and fetch the value from DB from timer to use it.

I was earlier thinking of passing the input data while wake up the timer from web app but unfortunately outsystems doesn't allow it . check the below post  

https://www.outsystems.com/forums/discussion/73182/is-it-possible-to-specify-a-input-parameter-when-wakeup-a-timer/

Generally speaking, timers are used for bulk operations. 

So if you have a table that you need to iterate and perform tasks for each record, then timers are your best friend.

If you want to perform some tasks on 1 item asynchronously, then you probably have a server action with an input parameter (or a session variable, if you prefer that) and you could consider using a (BPT) process, which does allow you to set an input parameter for your action.