Our team had a look at the issue and has the following feedback: the image used to test the configurator has a poor resolution and both the format and its content are extreme edge cases which do not make sense in the context of the algorithm/configurator. Therefore, making the Grasshopper definition work with this image would require a project extension. Please contact us in case this is something you would like to pursue.
This is not possible, because the issue is not an API integration issue, but rather part of the Grasshopper logic, which assumes a reasonable set of inputs. It might be possible to extend the Grasshopper logic to cover more edge cases or at least return errors when unexpected results happen. If you would like our team to work on this, please contact us to discuss a project scope.