SES overrides don't work as expected

[then3rdman]

It seems that the channel overides do nothing. At least for the email channel. I will also point out that the API documentation is different from that of the specific docs page.

One has the overrides nested under channels and the other does not. I have tried both and neither work.

Additionally the TS type for NewNotification is completely missing the overrides field.

I have also seen another bug report regarding the overrides for email.acttion_url is not working. This is over 2 months old....

To be very honest, a paid product with what is essentially a non funcitonal features for multiple months is a pretty big deal.

[unamashana]

Hey @then3rdman I am very sorry you are having this experience with MagicBell. We need to pick up pace with some of these issues. There is a known issue with the email channel overrides not making their way through.

However, the provider specific overrides for email work. Which email provider have you tried them for? We are happy to help with them.

Where are you doing the email rendering?

If it's in the third party, you should be able to use custom_attributes there - we relay them. Therefore you can override the URLs. If you are doing it in your code, you can simply send us the rendered HTML and skip other overrides all together. We can also relay this rendered HTML to the third party providers.

We have been slower on bugs with workarounds, and we are happy to help you find a solution. Several of our customers are using emails very successfully, and we can help you do so too. Thanks.

[then3rdman]

Thanks for the response. Sorry for the aggressive tone. So I have managed to resolve the overide of content not working howver unexpectedly it is completely bypassing the email template, both global and channel specific

[unamashana]

No problem - everything you mentioned is valid and a challenge if you don't know the workarounds. We appreciate the candid feedback.

Also, as I noted below, the content override is designed to give you full control on rendering. Therefore we do not override it with any other input.

[then3rdman]

So currently the content override means that the email is delivered with no template and the action_url override has no effect. Currently both are not usuable

[unamashana]

Hey @then3rdman content override is designed that way. I am glad it's working for you.

[then3rdman]

OK, does seems to odd to hard bypass two levels of templating with just a string input.

[baltamar3]

Hi, I have the same problem with overrides.providers.ses.Source (Not working)

[unamashana]

Hey @baltamar3 I am sorry for the trouble. We checked, and the code is setting up overrides. Do you see it in the request payload to SES in our Log page, for email deliveries? Can I also request you to check SES logs? While it's possible that we are not setting the overrides, it's also possible that AWS is not using what you set, because the email is not a verified sender, or for other AWS reason.

[baltamar3]

• notification creation endpoint, changing amazon ses source to Subrik Notifications <[email protected]>
  

• source override is not reflected in magicbell logs
  

[gamer22026]

Ditto for me with SES. Overrides for anything (including the example of Source) simply do not work.

[unamashana]

Sorry about that - we will work on reproducing and fixing this. Thanks!

[unamashana]

We are very sorry for the confusion. The override key was incorrect in the docs. The correct key to use is notification.overrides.providers.amazon_ses. For more info, please refer to the SES page on MagicBell docs