-
Notifications
You must be signed in to change notification settings - Fork 8
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad request because of schedule date #22
Comments
If I add this |
I made a PR that solves this issue: #23 |
I get this error too today, but I was not able to get the response body due to error http2: response body closed. @nam-truong-le you work around worked for me, thanks!! |
@llstarscreamll BTW by digging into the code I discovered that it actually returns an error of type obj, _, err := br.TransactionalEmailsApi.SendTransacEmail(ctx, body)
if err != nil {
if gserr, ok := err.(brevo.GenericSwaggerError); ok {
if merr, ok := gserr.Model().(brevo.ErrorModel); ok {
logrus.Errorf("Sending email: API Error: Code %s, Message: %s", merr.Code, merr.Message)
} else {
logrus.Errorf("Sending email: API Error decoding error response: %v (body %s)", gserr.Error(), string(gserr.Body()))
}
} else {
logrus.Errorf("Sending Email: %v", err)
}
return fmt.Errorf("Error sending email: %w", err)
} Result:
|
Hi! I had the same problem and I sent the email as Scheduled and set its value to |
@jain-raunak @LordPax could you guys please take a look into this? |
FYI I switched to postmarkapp.com as a result of this. The golang package is maintained by someone in the community, but actually is maintained, unlike this package. |
Hi team, I'm receiving this error after an upgrade from 1.0.3 to 1.1.2
My code is unchanged and this scheduled date is a beta feature. I don't set
ScheduledAt
in my code. Can you have a look? Thank you!The text was updated successfully, but these errors were encountered: