Hi, I can’t get the Wait node to work it keeps spinning and also gives error:
“Worflow execution has an error”
When I check the Postgres docker error log I have:
ERROR: invalid input syntax for type timestamp with time zone: “0NaN-NaN-NaNTNaN:NaN:NaN.NaN+NaN:NaN”
I have created a new database grant all permissions to user changed the database in the yaml file and re recreate the container, the log shows the migrations happenning, I connected to postgres docker to the new database the schema n8n has been created I checked the table execution_entity of schema n8n the lines of wait node are there but the field wait is empty , I have also an other error on the first screen, when i choose team size less than 20 it says
Error while submitting results
companySize: Potentially malicious string
Thanks again for your help, if someone has postgres in docker working please can you just share your yaml file it will be much appreciated thank you very much
HI @youssef_Cm, sorry to hear that you’re having issues with the Wait node.
Could you tell us a bit more about what you’re trying to achieve with the workflow? Or even better, share your workflow JSON by copy & pasting between (```)?
Have you checked whether the date/time inputs being passed to the wait node are in valid recognized formats? Also, have you checked that the timezone is correctly configured? Set the self-hosted instance timezone | n8n Docs
Hi Aya, thanks a lot for your answer because I am still stuck with no solution, yes I have used the the docker-compose.yaml available in Git, I posted it in my first post as well, I have also checked data and tried different format, ISO plus timezone, timestamp and other variations
This is the json of the workflow:
The error in your PostgreSQL log suggests that an invalid date or time value is being passed into the Wait node so these are the things I would try next:
What is the output of your second Date & Time node in your workflow and which format is it in? Can you pin your data? (check that it’s in YYYY-MM-DDTHH:mm:ss format)
I’ll also try to set the Postgres timezone to UTC, and then enter the timestamp in UTC format to rule out timezone mismatch