Currently the cancelPromise mechanism is there (in that cancelPromise options are provided and the value is passed in the invocation of a job.
The cancelPromise mechanism should be used and tested for two scenarios...
The overall schedule is halted by the requester resolving the CancelPromise
A timeout has expired, and the launched promise can therefore afford to give up.
However currently...
Internal promises aren't co-wired to the cancelPromise (e.g. queue promises, launchesFinalized.promise, settlementsFinalized.promise)
The timeout mechanism doesn't pass a job-invocation-specific cancelPromise (that composes with the global cancelPromise) meaning jobs will continue executing in the background and their results just ignored even when their specific timeout has expired
Currently the cancelPromise mechanism is there (in that cancelPromise options are provided and the value is passed in the invocation of a job.
The cancelPromise mechanism should be used and tested for two scenarios...
However currently...