To clarify what’s happening, if you have a custom table on a page which is skipped by the respondent, the HTTP action will throw a 500-error, ultimately failing and breaking the survey response as a result. If the custom table is being passed through the HTTP action in some way. We’re investigating this one ASAP.
This is all fixed up!
Please let us know if you are still running into issues with this feature.