DA14531 how to handle disconnects as a central

I am using SDK 6.0.16 (I haven't tried the newest SDK update because the rest of my code base is based on this version still) and I am trying to connect 3 DA14531 peripherals to a single DA14531 central. I based my code on the multirole example in the BLE_SDK6_examples Github and only used the central side of the multirole example code. I successfully modified this to be able to scan for 3 specific names that are preset on the peripherals, connect, and scan for their services/characteristics.

However, sometimes the multirole code will find the connection to a peripheral but it will not scan for the services/characteristics that I can read and write to. I want to be able to turn off and back on the peripheral that has not been successfully connected in order to essentially refresh its presence and let the central device reconnect and scan the peripheral. However, currently if I turn off any of the connected peripherals, it will throw an error in the "gapc_disconnect_ind_handler" where an "ASSERT_ERROR(0)" is thrown:

static int gapc_disconnect_ind_handler(ke_msg_id_t const msgid,
                                       struct gapc_disconnect_ind const *param,
                                       ke_task_id_t const dest_id,
                                       ke_task_id_t const src_id)
{
    uint8_t state = ke_state_get(dest_id);
    uint8_t conidx = KE_IDX_GET(src_id);

    if (state == APP_CONNECTED)
    {
        app_env[conidx].conidx = GAP_INVALID_CONIDX;
        app_env[conidx].connection_active = false;
        CALLBACK_ARGS_1(user_app_callbacks.app_on_disconnect, param)
    }
    else
    {
        // We are not in Connected State
        ASSERT_ERROR(0);
    }

    return (KE_MSG_CONSUMED);
}

I am correct in thinking that I should comment out this existing code in the sdk ("app_task.c") and re-implement without the "ASSERT_ERROR(0)" and instead figure out what the handle is of whichever connection was just dropped and then remove that from my global struct (because I'm using a global struct to keep track of all my existing connection id handles)? It is not clear to me what the if/else statement is doing and it seems that the "ASSERT_ERROR" is always going to be thrown unless the central is the one to disconnect.