Embedded Data Randomly Not Set by JavaScript

Is the drop down question force response?

Yes, that's right. Force Response is set for that question. I can see a selection was made in the data, but the embedded values were not set by the JS for some reason on a few responses.

https://www.qualtrics.com/community/discussion/comment/27300#Comment_27300What is length or how many number of elements are present in list and how many options are present in drop down?

It's quite long. There's 147 options in the drop-down and as many in three of the variable lists that are setting three different embedded fields. Then there's two other embedded fields that are set only for a few of the options selected.
The idea was, instead of having and maintaining 147 different email trigger actions, we would set some of the info for the email in this JS and switch to one email trigger action. Mostly it works... but not these seemingly random times.

What is the list in here, is it defined? I suggest to use the code in page submit. The below code works perfectly fine.
Qualtrics.SurveyEngine.addOnPageSubmit(function(type)
{
if(type == "next")
{
Qualtrics.SurveyEngine.setEmbeddedData("ApproverEmail",jQuery("#"+this.questionId).find("select").val());
}
});

Thank you, SurajK. Is this looking about right? I have multiple lists--do I need to refer to them in each .setEmbeddedData? Sorry for so many questions!
Qualtrics.SurveyEngine.addOnPageSubmit(function(type)
{

//This is the list of approver emails
var list = {
1: "example value 1",
2: "example value 2",
};

if(type == "next")
{
Qualtrics.SurveyEngine.setEmbeddedData("ApproverEmail",jQuery("#"+this.questionId).find("select").val());
}

//This is the list of approver names
var list2 = {
1: "example value 1",
2: "example value 2",
 };

if(type == "next")
{
Qualtrics.SurveyEngine.setEmbeddedData("ApproverName",jQuery("#"+this.questionId).find("select").val());
}

//etc.
});

Got it! I will try this out and see how it goes. Thank you so much!!! :)

I've modified my code, and it seems to be working so far. Thank you again. I assume this event always triggers and that the unload event could possibly be avoided somehow (perhaps by someone closing their browser instead of leaving the page first?). Is that correct? I'm just curious and would like to understand more.

The unload function works when you click next button or even when you click back button. This may be problem in case of back and forth. The page submit function can make work in case of next click or even if you want to make it work when back click. Also, you can write other code as well in case of back click. I prefer page submit function.

I think I understand. Thank you!