In our Flutter integration, mute does not work as expected even though the Vapi SDK claims to support it. When mute is triggered from the Flutter layer: Mic input continues streaming Agent keeps processing audio Voice generation/transcription does not pause or stop So effectively, mute is a no-op at runtime.

Actionable Next Step: Test the mute functionality directly in the [Vapi dashboard](https://dashboard.vapi.ai/) to determine if the issue is with your Flutter integration or the Vapi platform itself. - In the dashboard, trigger mute during a live call and observe if the agent stops processing audio. - If mute works in the dashboard but not in Flutter, check your API logs for mute command requests from your app to ensure they're being sent and received as expected. This will help you isolate whether the problem is SDK-specific or a broader integration issue ([Vapi Debugging Documentation](https://docs.vapi.ai/debugging)). Source: - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging)

Hi khushalj, Please try these diagnostic steps to isolate whether this is an SDK bug or integration/config issue: 1. Reproduce in dashboard - Start a live call in the Vapi dashboard: https://dashboard.vapi.ai/ - Trigger mute from the dashboard UI and confirm whether the agent stops processing audio (transcript stops, no more STT events). - If mute works in dashboard → likely Flutter SDK or your app layer. If mute fails in dashboard → platform issue. 2. If dashboard mute works, collect Flutter-side evidence - Enable verbose logging in your Flutter app and capture SDK logs around the mute action. - Check API / webhook logs in dashboard: Observe > API Logs and Webhook Logs for incoming mute requests/events and responses. - Confirm the app sends the expected mute command (check payload, auth, timestamps). If using the Widget/SDK event, verify the exact event name and payload match the SDK docs. 3. Verify Flutter SDK usage - Ensure you call the SDK mute method (not only UI state). Confirm method returns success and that you await/handle its completion. - If you manage local microphone tracks, verify you stop/disable the MediaStreamTrack as well (some apps need to mute both locally and notify Vapi). - If using a tunnel/relay (ngrok, etc.), verify low-latency delivery—delays can make it appear mute didn’t apply. 4. Collect artifacts if issue persists - Dashboard call ID and timestamp for a failing Flutter call. - Flutter SDK logs around mute (include request/response if present). - API/Webhook log excerpts showing mute command delivery (or absence). - Minimal reproduction steps or a short screen recording showing the behavior.