Since commit f486472, we also add a pending-sensed-fact for actions that do not wait for the effect to occur. This can be used to react properly if the effect does not ever occur as expected. One possible scenario:
- Prepare a machine, do not wait until it is
READY-AT-OUTPUT.
- Drive to the output side
- Machine is not yet ready, monitoring needs to decide what to do (e,g., wait or fail). For this, we need to know whether we expect the machine state to change.
However, as it currently stands, if the effect does not occur, there are at least two problems:
- the pending effect will never be cleaned up
- the action is marked as successful, but at least one of its effects never occurred
This needs improvement, as pointed out in #12.
Since commit f486472, we also add a
pending-sensed-factfor actions that do not wait for the effect to occur. This can be used to react properly if the effect does not ever occur as expected. One possible scenario:READY-AT-OUTPUT.However, as it currently stands, if the effect does not occur, there are at least two problems:
This needs improvement, as pointed out in #12.