Invalid delay configuration
I started to this get message yesterday,
"error": "Cannot read properties of undefined (reading 'findOne')". But my payload hasn't changed here is my payload: "payload": {
"subject": "We're On It! Your Roof Quote Request is Being Processed",
"comment": "You are successfully submit form requesting quotes for your new roof",
"jobId": "65f04a4af210a27e136a9a1f",
"sendAt": "2024-03-12T12:28:04.579Z"
}
22 Replies
@thesockguy Are you using novu cloud web.novu.co ?
Yes
Could you please share transactionId for this event?
yes
one second
c623b0c3-88f9-4873-ac90-6e2b87fdc191
122d2e32-10b3-4d91-a241-cc3a6f16a2ad
Here are 2 ^^
Thanks, I am checking
Here are a couple transaction IDs of it working:
c888a943-8563-472c-8670-29e455609672
8dbcadc3-23e5-4c0d-92f4-6a8b44e93508
@thesockguy
I guess you sent time value that has been passed for this transactionId
c623b0c3-88f9-4873-ac90-6e2b87fdc191
"sendAt": "2024-03-12T12:28:04.579Z"that is correct
Okay, that is the reason of this error
always send future date and time value for delay step variable
At the time it was in the future
@thesockguy, you just advanced to level 2!
I sent that at 7:40 my time
It is now 8:14 here. Which means it is 13:14 UTC
so I sent it at 12:14 UTC
i mean at 12:40 UTC
It had a trigger time of 12:47 UTC
@Pawan Jain I have been testing a lot the last couple of days and have had no issues til end of day yesterday(didn't notice it til today)
I have logic on my end to always send a future datetime
and I have seen the error for that issue, it clearly states that. This does not
@thesockguy
Thanks for sharing the issue. I can reproduce the issue
sharing with team to fix this asap
Ok, thank you! Do you know if this is a small syntax issue where it could be fixed right away?
What I mean will this issue be fixed before my meeting in 35 minutes?
As per my knowledge, no it is not a small syntax issue for sure
as it will be fixed from code side
Ok, I will remove the delay for now and explain the situation. thank you
How can I monitor progress of this bug?
Give me few minutes, I will share github issue with you 🙂
Thank you 🙂
team is working on deploying hot fix for this
@thesockguy this bug is fixed.
Please try again and let me know if you still see this happening again
Testing now
looks good! THANK YOU SO MUCH FOR THE QUICK RESPONSE ON THIS
Glad it is fixed for you