Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug Report: save id from resend response #5337

Closed
2 tasks done
jainpawan21 opened this issue Mar 25, 2024 · 4 comments
Closed
2 tasks done

馃悰 Bug Report: save id from resend response #5337

jainpawan21 opened this issue Mar 25, 2024 · 4 comments

Comments

@jainpawan21
Copy link
Member

馃摐 Description

When resend email provider is used, As per resend API and SDK method , id is returned in response, but novu is not storing this Id in execution details

馃憻 Reproduction steps

  1. Make resend as primary email integration with valid resend credentials
  2. Add email step in workflow
  3. Trigger the workflow
  4. Check activity feed
  5. Click on the show details button on the message sent log of email step

馃憤 Expected behavior

Novu should show resend response id in the execution details

馃憥 Actual Behavior with Screenshots

Id not stored and not showing in execution details

Novu version

Novu Saas

npm version

No response

node version

No response

馃搩 Provide any additional context for the Bug.

No response

馃憖 Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find a similar issue

馃彚 Have you read the Contributing Guidelines?

Are you willing to submit PR?

None

Copy link

linear bot commented Mar 25, 2024

@michaldziuba03
Copy link
Contributor

you can assign me

@michaldziuba03
Copy link
Contributor

@jainpawan21 unable to reproduce the issue

image

image

@jainpawan21
Copy link
Member Author

@michaldziuba03

Thanks for help. I see it is not reproducible 馃檪

Closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants