Sanjeet What about keeping track of 'last execution' and 'current time' to give you enough to decide if it has been at least 60 mins? Are there additional complications to consider?
Thanks On Thu, Aug 12, 2021 at 9:43 AM sanjeet rath <[email protected]> wrote: > > Thanks , Joe for the quick reply. > I was wondering how can i figure out inside the processor's Ontrigger > method when it was run previously. > Basicaly want to implement ur suggestion of restricting the execution > inside the processor's code . > > Regards, > Sanjeet > > On Thu, 12 Aug 2021, 9:43 pm Joe Witt, <[email protected]> wrote: > > > Sanjeet > > > > We dont presently allow the processor developer to put such a > > restriction into the code. Your best bet for now would be to document > > that the processor even if scheduled more than once in a one hour > > period will not execute its function more than once. Then in your > > code you can protect/ensure it only truly does the execution once and > > hour. > > > > Thanks > > Joe > > > > On Thu, Aug 12, 2021 at 9:10 AM sanjeet rath <[email protected]> > > wrote: > > > > > > Hi , > > > > > > I am building a custom processor and there is restriction i want to put > > for > > > the processor that it should not schedule to run 2 times in 1 hour time > > > period. > > > > > > I can acheive this by passing "run schedule" 60 mins. > > > > > > Is there any other way i can do in my custom processor code, So that it > > > won't allow the user to select "run schedule " time less than 60 > > > mins.basically similar to we can restrict the procesor to execute on > > > prinary node. > > > > > > Any other thought is really helpfull. > > > > > > Thanks, > > > Sanjeet > >
