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
I set up a Template Switch using the UI. It has an option to let stations run in parallel when being started manually. However the run() function doesn't actually seem to expect the option.
I'm assuming either the frontend or backend is wrong here. Does anyone have a clue?
The text was updated successfully, but these errors were encountered:
First of all, do not confuse continue_running_stations with running stations in parallel. All this parameter does is not stop already running stations--kind of. Depending on the order of the already running stations vs. the new stations, an already running station may be paused and pre-empted by the new one, but will be queued to continue later with whatever time is remaining. This is because the new list of run-times for all stations must be submitted in station order, so they will then run in station order.
In any case, what you have encountered is that the run service (action) takes different parameters depending on the chosen target entity. The continue_running_stations parameter only works when a controller is the target--not a program or station--and then only if index/seconds pairs are used.
I have submitted PR #314 to try to alleviate the confusion by eliminating the display of parameters that are not valid. It's a work in progress. In the meantime, leave off that parameter unless targeting a controller.
I set up a Template Switch using the UI. It has an option to let stations run in parallel when being started manually. However the
run()
function doesn't actually seem to expect the option.I'm assuming either the frontend or backend is wrong here. Does anyone have a clue?
The text was updated successfully, but these errors were encountered: