It looks like the player on your website is using Flash, so when one of the URLs is Tweeted, the twitter:card player tags in your web pages point to a Flash object.

We announced that we would sandbox (no longer be supporting) these kinds of players for new partners in August last year. In April we announced that we would discontinue support for Flash in any of our cards, and switched off support in June.

Moving to HTML5 and more modern technologies means that we are able to provide a better experience across the board on both web and mobile platforms.

We strive to maintain a secure and dynamic platform for our developer community and all of our users. Today we’re announcing some important changes to the Player Card. By improving security and speeding up approval times for this tool, you can now more safely and quickly deliver rich media to users across the globe.
Improved security Player Cards have always rendered third party media players in an iFrame on twitter.com. Now we’ll enforce sandboxing on the iFrame for all newly approved publ…

HTML5 has become the standard for video and audio on the web moving away from plugin based players. Native video on twitter.com is already served via HTML5 video players and this is the right time to complete the transition to HTML5 across all Twitter media player products. With this update, we’ll ensure delivery of the best video experience to our users by providing better performance, improved security, and mobile compatibility where more than 80% of Twitter users consume your video and audio …

There are some suggestions for how to migrate your players to more modern technologies in our announcement post, which is the third link above. We also have a sample player card shared in our Github:

cards-player-samples - Sample Code for Player Cards, both for stored and streamed video.

Apologies for any gap in communication here that caused you to miss the update, we do work hard to provide notice with changes like these, and posted as much information as we could over an extended period to support cases like this.

Thanks for the update. Probably we missed the notification. We have tried to make changes to the player as recommended in the github example but, still no luck. We have used m3u8 URL as stream. Here’s the new URL: https://events.sap.com/page2.html