I've set a command to be executed when an item is updated, but I've noticed that after the check that discovers the item is updated, the item seems to retain an 'updated' status until I manually go to Items>Set state>Default (reset to neutral). If I don't reset it, subsequent checks of the item appear to result in the command being executed again, as the item still has an 'updated' status.
The desired behaviour is for the command to be executed when a change in the item's webpage has been detected, then for the item to be automatically set back to neutral status as the required follow-up behaviour (executing the command) has already been carried out. Had I needed to manually reset it to neutral, then I could just manually execute the command as well, defeating the purpose of setting a command to execute automatically when a change is detected.
I'm not sure whether this is a bug or issue only I'm experiencing, or whether it's default behaviour.
Last edit: xyz 2021-01-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well there are two options for a command:
Issue when the item is updated an d issue on update only.
So, the first one results in the behaviour as described. The second one would only issue the command if the page changed (again).
So this should do, what you want.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, I had misinterpreted what (only once) meant, thinking that it meant the command only executed upon the first change to the webpage and not subsequent changes
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've set a command to be executed when an item is updated, but I've noticed that after the check that discovers the item is updated, the item seems to retain an 'updated' status until I manually go to Items>Set state>Default (reset to neutral). If I don't reset it, subsequent checks of the item appear to result in the command being executed again, as the item still has an 'updated' status.
The desired behaviour is for the command to be executed when a change in the item's webpage has been detected, then for the item to be automatically set back to neutral status as the required follow-up behaviour (executing the command) has already been carried out. Had I needed to manually reset it to neutral, then I could just manually execute the command as well, defeating the purpose of setting a command to execute automatically when a change is detected.
I'm not sure whether this is a bug or issue only I'm experiencing, or whether it's default behaviour.
Last edit: xyz 2021-01-06
Well there are two options for a command:
Issue when the item is updated an d issue on update only.
So, the first one results in the behaviour as described. The second one would only issue the command if the page changed (again).
So this should do, what you want.
Thanks, I had misinterpreted what (only once) meant, thinking that it meant the command only executed upon the first change to the webpage and not subsequent changes