You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We know that if a domain invitation notification fails for a particular domain manager then it blocks a domain invitation from sending. However, we got into a scenario on getgov-development where we could not determine why an invite would not send. When adding a domain invitation for "expert-down-little.gov" first only a warning message appeared saying "could not send email invitation", no error message saying it was unable to send to a manager. The logs read "Could not send email invitation (Other Exception)" indicating an unexpected exception occurred. When another attempt was made to this email address, but by a different user, the following error (not warning) appeared "is already a member of another .gov organization."
Further, when others tried different emails we did get an error message saying it failed to send to a manager. Then when other attempts were made to send a domain invitation to [email protected] and [email protected], but in both cases the the portfolio invitation failed and no traceback was logged to indicate why. The error in this case changed to be "Could not sent email invitation to [email protected] for portfolio Farm Credit Administration. Portfolio invitation not saved."
Expected Behavior
The portfolio invitation shouldn't fail. "Could not send email invitation (Other Exception)" shouldn't have occurred in this scenario.
Keep in mind the other bug tickets this is bundled with, but investigate this error to determine if there is a runtime or general logic error that may have been missed. Add additional error logs where deemed helpful.
If this is resolved in the other bug fix (#3378 ), then mark this as closed.
Steps to Reproduce
open development and in django admin domain invitations table
send a domain invitation for expert-down-little.gov
see errors
Environment
getgov-development
Additional Context
slack thread with screenshots, who ran into this error and on what email address.
Issue Links
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
We know that if a domain invitation notification fails for a particular domain manager then it blocks a domain invitation from sending. However, we got into a scenario on getgov-development where we could not determine why an invite would not send. When adding a domain invitation for "expert-down-little.gov" first only a warning message appeared saying "could not send email invitation", no error message saying it was unable to send to a manager. The logs read "Could not send email invitation (Other Exception)" indicating an unexpected exception occurred. When another attempt was made to this email address, but by a different user, the following error (not warning) appeared "is already a member of another .gov organization."
Further, when others tried different emails we did get an error message saying it failed to send to a manager. Then when other attempts were made to send a domain invitation to [email protected] and [email protected], but in both cases the the portfolio invitation failed and no traceback was logged to indicate why. The error in this case changed to be "Could not sent email invitation to [email protected] for portfolio Farm Credit Administration. Portfolio invitation not saved."
Expected Behavior
The portfolio invitation shouldn't fail. "Could not send email invitation (Other Exception)" shouldn't have occurred in this scenario.
Keep in mind the other bug tickets this is bundled with, but investigate this error to determine if there is a runtime or general logic error that may have been missed. Add additional error logs where deemed helpful.
If this is resolved in the other bug fix (#3378 ), then mark this as closed.
Steps to Reproduce
Environment
getgov-development
Additional Context
slack thread with screenshots, who ran into this error and on what email address.
Issue Links
No response
The text was updated successfully, but these errors were encountered: