I have a Time inject setup to run from 20:00 (starting time) to 14:00 (Ending time) - to inject every minute.
The first time i ran this it worked fine (as expected) and kicked off at 8PM that evening and continued operating every minute overnight
However the next day i did a redeploy at 9:00 AM of the flow and the node now thinks it is not due to kick off until 8PM again this evening i.e. it appears to think that this is brand new start and it does not fire again until the start time is hit - rather than looking at this as being part of the time window
Node Red 3.02 on Ubuntu.
Craig
Screenshots
If applicable, add screenshots to help explain your problem.
Expected behavior
A clear and concise description of what you expected to happen.
System information (please complete the following information):
Node Version [e.g. 0.4.7]
Node-Red Version
Additional context
Add any other context about the problem here.
I have a Time inject setup to run from 20:00 (starting time) to 14:00 (Ending time) - to inject every minute.
The first time i ran this it worked fine (as expected) and kicked off at 8PM that evening and continued operating every minute overnight
However the next day i did a redeploy at 9:00 AM of the flow and the node now thinks it is not due to kick off until 8PM again this evening i.e. it appears to think that this is brand new start and it does not fire again until the start time is hit - rather than looking at this as being part of the time window
Node Red 3.02 on Ubuntu.
Craig
Screenshots If applicable, add screenshots to help explain your problem.
Expected behavior A clear and concise description of what you expected to happen.
System information (please complete the following information):
Additional context Add any other context about the problem here.