With the addition of schedule participant persistence in PR #242, participant profiles are no longer able to change after the first time they are introduced, even if all the nodes are restarted.
The workaround for now is to delete the persistence file or directly edit it to have the desired parameters. By default that file is called .rmf_schedule_node.yaml and will be located in the working directory where the schedule node was launched from.
Instead of needing to manual delete or edit this file, the schedule system should be able to update this information automatically when it receives new information for a participant.
mxgrey
commented
3 years ago
With the addition of schedule participant persistence in PR #242, participant profiles are no longer able to change after the first time they are introduced, even if all the nodes are restarted.
The workaround for now is to delete the persistence file or directly edit it to have the desired parameters. By default that file is called
.rmf_schedule_node.yamland will be located in the working directory where the schedule node was launched from.Instead of needing to manual delete or edit this file, the schedule system should be able to update this information automatically when it receives new information for a participant.