mattsota's account

The back-end configuration change fixed it. Thank you so much for helping to troubleshoot that!

Yes, that works, I now receive:  {"status":"SIGNING_COMPLETED"}

Good eye thank you. I see it does state to user 'signer' and not 'signerId' in the API documentation. I will keep a closer eye on the syntax going forward. 

Package with Role Index at 1 and 2: kmzQ6zfln_8xGASeKSMPjzejVCw=

Package with Role Index at 0 and 1: FHZcBUuwETEkVf99pbewWlBgA24=

It was for the second one that I explicitly tested sending an email at Thu 3/17/2022 1:19 PM EST. So if you see that in the logs, that was not automatic, it was me clicking the 'resend' button in the Dashboard.

Thank you for that information. Reading about 'email.activate', it states: 

If a package is configured to use in-order signing, only the first signer will receive an invitation when the package is initially sent. The second and following signers will receive an invitation email when the previous signer has completed their part of the process.

Now, the first Signer is receiving the email notification, and the email looks like it matches the "default template" described in the documentation. Doesn't that mean the 'email.activate' is already working? I'm just confused how Signer1 gets the automatic email, but Signer2 does not. 

Separately, in the near future I will work on customizing the email message. It looks like we can do that with the package via the API, according to the "Customizing Invitation Emails" info. Please clarify if that is true, and how that API works with the 'default template' in 'email.activate'. Thanks.

Just to follow up and finalize this, enabling the "email.activate" on our account did indeed solve the issue. After Signer1 signed, then Signer2 automatically received a notification.