On the SDK side, I’d verify version alignment before treating this as a 5.1.2 regression. The import the Meeting SDK for webflow requires the correct versioned assets, and Zoom has a prior staff-confirmed case where a disabled audio button came from mismatched setZoomJSLib assets.
You can check to make sure every JS, WASM, and lib/av path is pinned to 5.1.2 with no cached 4.x or older source.zoom.us assets. You can also check to see if you can reproduce the same meeting in the official Meeting SDK web sample. If it fails there on 5.1.2 but not 4.0.0, that is the strongest regression report you can hand Zoom.
One thing to note - the Meeting SDK for web docs explicitly says this SDK is reserved for human use cases and does not support bots or AI notetakers, and point these use cases to RTMS instead.
If you need help, check out Recall.ai. We’re a Zoom RTMS Preferred Partner.