Production RTMS never starts despite active Developer Pack and correct configuration

I’m using a user-managed General App with Zoom Meetings RTMS.

RTMS previously worked in Development, but the Production/Beta version of the app does not start RTMS at all.

I have verified all of the following:

  • Zoom Developer Pack Free Trial is active and credits remain
  • Production OAuth token contains:
    • meeting:read:meeting_audio
    • rtms:read:rtms_started
    • rtms:read:rtms_stopped
    • user:read:user
  • Production Event Subscription is enabled
  • meeting.rtms_started and meeting.rtms_stopped are subscribed
  • Production webhook URL is validated and publicly reachable
  • “Share realtime meeting content with apps” is enabled
  • The Production app is installed/authorized
  • The Production app is selected for RTMS auto-start
  • The same authorized Zoom user hosts the meeting
  • I tested from both the Zoom desktop client and iPad
  • The Developer Pack shows 20 credits with only about 0.84 used

The Production webhook endpoint is:

https://zoom-rtms-webhook-server.replit.app/webhooks/zoom/rtms-production

The endpoint is continuously hosted on a Reserved VM and responds successfully to health checks.

However, when I start a meeting, no meeting.rtms_started event is generated at all. I checked the Production server logs and there is zero inbound Zoom webhook activity associated with the meeting. Therefore the failure appears to occur before my application receives any RTMS event.

Could Zoom please verify the following on your side?

  1. RTMS entitlement is fully provisioned for my Zoom account.
  2. My RTMS concurrency is greater than zero.
  3. The Production version of my General App is correctly associated with my Developer Pack / RTMS entitlement.
  4. RTMS auto-start is actually enabled server-side for this app/account.
  5. There is no Production/Beta RTMS provisioning issue preventing meeting.rtms_started from being generated.

The app is currently named General app 693.

I’m happy to provide the Production App ID, account ID, meeting IDs/UUIDs, timestamps, or any other non-secret diagnostic information needed.

Thank you,
Ari

@Ari2 I’ve just done a check on your account. As long as your application is not published, it will still use the development webhook only. You will need to handle the events on your development webhook url, with the development clientid and client secret. In addition do make sure you generate the oauth URL and add it again.