export / assign: It seems as if incoming results that have only one row will crash this process with an IndexError raised from _updated_index_tuples(). See the "Database Survey" job / Slack thread. The root of this might be in the cut/join-process before the export though. This needs checking.
cut / join: There is an example of three (regular / transposed; structurally equivalent) array summaries that will fail when trying to join the cut results back together. I have already tried to overwrite the array question texts in order rule out any non-matching index problems, but this will lead into an error late at build stage. See Zoe's internal IT OM job // Slack thread.
export/assign: It seems as if incoming results that have only one row will crash this process with anIndexErrorraised from_updated_index_tuples(). See the "Database Survey" job / Slack thread. The root of this might be in the cut/join-process before the export though. This needs checking.cut/join: There is an example of three (regular / transposed; structurally equivalent) array summaries that will fail when trying to join the cut results back together. I have already tried to overwrite the array question texts in order rule out any non-matching index problems, but this will lead into an error late at build stage. See Zoe's internal IT OM job // Slack thread.