Next step is skipped as well when the first one is skipped
Hello everybody!
I'm having a strange issue with the code-first workflow.
I have a workflow with 2 steps:
send-email
and send-sms
.
Each one should be dispatched only if the payload.type
matches with itself, for example:
It should send the email and skip the SMS, and:
It should send the SMS and skip the email.
It turns out that when I trigger the workflow to send the email, the SMS is skipped correctly, but when I trigger the same to send the SMS, both email and SMS are skipped.
If I invert the steps orders, the problem will be inverted as well, with SMS being sent as expected, but the email will be skipped when should be sent.
I tested the same flow in Local Studio, also in a deployed environment, triggering through the Novu Dashboard, but I was unsuccessful in identifying the reason.
The single thing that I'd identified it's in the Bridge API log the following error: Failed to hydrate stepId: 'send-sms'
, after that, Novu tries to send again, and then the bug occurs.
I'm sure the issue isn't related to the workflow code to render the body, because I tested with static text, both for email and SMS.
Could you help me to understand the issue, my mistake, or if it's really a bug?
Thank you.12 Replies
Environment ID:
66a79f82dfafba8038bc33a4
@Rainmaker
Thanks for sharing the issue in detail. It helps in debugging.
Can you please share the code snippet you are using for above workflow?
Sure @Pawan Jain
It's something like that:
Thank you for your response.
@Rainmaker I can reproduce the bug.
Sharing it with team
Thank you @Pawan Jain .
Just curious, is there a ETA to fix bugs like that?
@Rainmaker
I will keep you updated on this. I hope it to be fixed end of this week
Hello @Pawan Jain
Do you have any news?
Thanks.
@Rainmaker, you just advanced to level 1!
@Rainmaker
Richard from our team have raised a PR for this
https://github.com/novuhq/novu/pull/6371
Thank you so much @Pawan Jain
When it's released, I'll be back to you if it worked.
@Rainmaker
This bug is not fixed. Can you please retry?