Yeah, that’s a known issue — the UI wipes the properties, so only the first destination ever works. Your cURL fix is the right approach since the schema has to be enforced API-first. Quick workaround: define the schema outside the UI and sync it back so the destination enum doesn’t get lost. Are you aiming to make this production-stable or just testing flows?