RUNNERAT has no effect has soon as
runner.endpoint configuration is defined (typically on Warp 10 distributed version).
Runners period is defined by the path of the WarpScript file. Typically,
/opt/warp10/warpscripts/myapp/60000/myrunner.mc2 will be scheduled every 60 seconds, starting at the Warp 10 instance start.
RUNNERAT allow to dynamically schedule the next run to an absolute timestamp before the period defined in the path. Combined with
RUNNERAT can be used to schedule the next run to an absolute timestamp whatever the period defined in the path. See examples below.
RUNNERAT careless use may bring problems: If a runner is planified every hour, and the execution time is 10 minutes, calling RUNNERAT to reschedule the runner every minute will lead to saturate a runner thread.
That's why the usage is restricted to a capability. Use
CAPADD to add
runner.reschedule.min.period capability from a read or write token at runtime.
runner.reschedule.min.period capability must contain the minimum of millisecond offset to now allowed for
RUNNERAT. See example below. This capability also overrides
Examples are available here on our blog.