You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a flogo application contains timer(repeating=false) trigger, it did run as expected but application itself does not exit after all activities executed, is it possible to terminate the entire application automatically after everything is done, rather than keep running like a daemon?
Thanks.
D:\dev\go\src\github.com\lwlwlwlw\flogo-project\once and replay\bin>"once and replay.exe"
2017-10-24 11:23:15.877 INFO [engine] - Engine: Starting...
2017-10-24 11:23:15.887 INFO [engine] - Engine: Starting Services...
2017-10-24 11:23:15.887 INFO [engine] - Engine: Started Services
2017-10-24 11:23:15.887 INFO [timer-trigger] - Scheduling a run one time job
2017-10-24 11:23:15.887 WARN [engine] - Trigger data not applied to context
2017-10-24 11:23:15.887 INFO [engine] - In Flow Run uri: 'f_1'
2017-10-24 11:23:15.887 INFO [engine] - FlowInstance Flow: &{tibco-simple 0xa31280 map[1:0xa31280]}
2017-10-24 11:23:15.887 INFO [activity-tibco-log] -
2017-10-24 11:23:15.887 INFO [engine] - Trigger [timer] started
2017-10-24 11:23:15.888 INFO [engine] - Engine: Started
2017-10-24 11:23:15.888 INFO [engine] - Flow [7157d0ba79842406350e482cc79889c2] Completed
******application is still running here ******
The text was updated successfully, but these errors were encountered:
For a flogo application contains timer(repeating=false) trigger, it did run as expected but application itself does not exit after all activities executed, is it possible to terminate the entire application automatically after everything is done, rather than keep running like a daemon?
Thanks.
D:\dev\go\src\github.com\lwlwlwlw\flogo-project\once and replay\bin>"once and replay.exe"
2017-10-24 11:23:15.877 INFO [engine] - Engine: Starting...
2017-10-24 11:23:15.887 INFO [engine] - Engine: Starting Services...
2017-10-24 11:23:15.887 INFO [engine] - Engine: Started Services
2017-10-24 11:23:15.887 INFO [timer-trigger] - Scheduling a run one time job
2017-10-24 11:23:15.887 WARN [engine] - Trigger data not applied to context
2017-10-24 11:23:15.887 INFO [engine] - In Flow Run uri: 'f_1'
2017-10-24 11:23:15.887 INFO [engine] - FlowInstance Flow: &{tibco-simple 0xa31280 map[1:0xa31280]}
2017-10-24 11:23:15.887 INFO [activity-tibco-log] -
2017-10-24 11:23:15.887 INFO [engine] - Trigger [timer] started
2017-10-24 11:23:15.888 INFO [engine] - Engine: Started
2017-10-24 11:23:15.888 INFO [engine] - Flow [7157d0ba79842406350e482cc79889c2] Completed
******application is still running here ******
The text was updated successfully, but these errors were encountered: