X,Y coordinates specified in a Conditions file is causing "Object { origin: "util.toNumerical", context: "when converting an object to its numerical form", error: "unable to convert undefined to a number"" error

I went to put my experiment online yesterday and began seeing a error after my welcome message page:

Unfortunately we encountered the following error:

  • when converting an object to its numerical form*
  • unable to convert undefined to a number*

Try to run the experiment again. If the error persists, contact the experiment designer.

When I looked into the HTML, I found these messages:

*DEBUG unknown | import attributes from: {“instruText”:"(text for directions)",“text_xpos”:0,“text_ypos”:0}

Object { origin: “util.toNumerical”, context: “when converting an object to its numerical form”, error: “unable to convert undefined to a number” }*

FATAL unknown | {“origin”:“util.toNumerical”,“context”:“when converting an object to its numerical form”,“error”:“unable to convert undefined to a number”}

Since this appears to be triggered by my text coordinates, I did some digging. It seems like my conditions file where the text coordinates are listed is being ignored or is causing this util.toNumeric issue. Currently, the x position and y position are each stored in their own column and each row is one page/loop repeat.
Currently, my experiment is frozen on this “unfortunately we encountered the following error” page and will not continue.

Other background, this experiment is built in builder and uses condition files for the directions and trials.These files all contain text, x/y coordinates, and correct key responses that are used as variables within each builder routine. It works totally fine locally, but started having these issues when it moved online.

Any help fixing this would be amazing! Thank you.

Solved!
I solved this error by creating a routine for each page of the directions instead of having all the directions run through a conditions file. It seemed like the empty cells (ie, the pages where a stimuli didn’t have to be displayed) were not liked by JS.