Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
While testing a custom processor with the annotation `TriggerWhenEmpty`, noted an issue with the scheduling of the processor.
The processor setting `Yield Duration` defaults in the UI to `1 sec`. The expectation of the `onTrigger()` method is that, if the API `ProcessContext.yield()` is called, the processor should not be scheduled for the amount of time specified in Yield Duration.
On adding the custom processor to the canvas and starting it, the processor is scheduled continuously. When the processor is stopped and Yield Duration is edited, starting the processor results in Yield Duration being honored. Reverting the edit (to set Yield Duration to the default) is also honored.
It is as if the default Yield Duration setting is ignored when the setting has never been set.
Attachments
Issue Links
- links to
