Configured form that doesn't exist in REDCAP hanging

[alexfelmeister]

2

If a configuration contains a form/event combo that does not actually exist in REDCap, system hangs.

Current example: https://brp.research.chop.edu/admin/api/protocoldatasource/211/change/?_changelist_filters=protocol__id__exact%3D81

{
    "unique_event_names": ["demographics_arm_1"],
    "event_labels": ["Demographics"],
    "form_data": {
        "demographics_form": [1],
        "medical_history": [1]
    },
    "record_id_field_name": "record_id",
        "form_order": [
             "0_0",
             "1_0"
        ],
    "labels": [
        1,
        2
     ]

* Medical History in Chordoma configured but doesn't exist. "medical_history": [1]

[alexfelmeister]

@seg1129 going through configuration with d3b and finding some items.