Hi, trying to set an inject node to repeat monthly (730 hours).
The field doesn't tell me it can't deal with that and there are no visible errors until I click "Done" - then the node is marked as invalid but no indication of why.
Would that be 730 hours after you last deployed?
Surely a job to entrust to cron plus!
My Pihole device updates the list of top level domain name servers every 6 months via cron plus. Mind you I think I've only seen the notification SMS once
Every 730 hours with an initial run 10 seconds after Node-RED starts.
Sure but I shouldn't really need a contrib node to do this. And I think inject uses a cron library anyway? I don't need all the complexity of cron+ and a monthly inject wouldn't really be an uncommon need.
I'm discovering other bugs in the settings for the inject node as well.
If you try to find the max number of hours it will take, you get some very weird results. For example, 600 hours initially also gave a warning triangle but when I reduced to 550 (no triangle) and then crept back up to 600, there was no warning BUT after deployment, it had reset to 10 hours.
Also, some settings change the settings to minutes instead of hours. This was set to 599 hours but changes to minutes after deploy.
Which is, of course, 599 hours. And that gives a warning triangle by the way.
Ah, I see, I only get an actual error message if I ignore the warning triangle and go ahead and deploy.
Otherwise, you are left guessing.
BTW, 595 hours appears to be the max you can set.
The node help does say that:
Maybe use a context/environment variable and check daily if it has expired?
Yes, there are, of course, other options. The real point here is that there are some bugs that could do with squashing.
595 hours is fine for what I want, it doesn't have to be exact. But the lack of clear errors and the number inconsistencies as you get to the edge is confusing to users.
