Manage Broadcasts

jmluettgen

New Member
If you are using YouTube, then go to Studio.YouTube.com.
You can delete the scheduled broadcast in YouTube Studio. Select Content, then Live, then using the : (three dots) next to the scheduled broadcast elect Delete Forever.
 

billp555

New Member
This is an older thread,but I had the same problem as RigPa. To fix this, create a new live stream with the exact same name and then delete it. In my case, I went to YouTube Studio and created a new Live Stream (unlisted or private) and gave it the exact same name as the undeleteable broadcast in OBS Studio's Manage Broadcast --> Select Existing Broadcast window. In the same OBS Select Existing Broadcast window, click 'Select Broadcast and Start Streaming'. After about 1 minute, stop the stream from inside OBS Studio. YouTube Studio creates the short live stream. Then you can delete it in YouTube Studio as jmluettgen suggested. In a few moments it gets deleted from the OBS window (you may need to close OBS and re-open it again to see the result).
 

query-01

New Member
Old is an older thread,but I had the same problem as RigPa. To fix this, create a new live stream with the exact same name and then delete it. In my case, I went to YouTube Studio and created a new Live Stream (unlisted or private) and gave it the exact same name as the undeleteable broadcast in OBS Studio's Manage Broadcast --> Select Existing Broadcast window. In the same OBS Select Existing Broadcast window, click 'Select Broadcast and Start Streaming'. After about 1 minute, stop the stream from inside OBS Studio. YouTube Studio creates the short live stream. Then you can delete it in YouTube Studio as jmluettgen suggested. In a few moments it gets deleted from the OBS window (you may need to close OBS and re-open it again to see the result).
Old post or not, this issue continues to happen in ver: 30.1.2 (64 bit). The ongoing concern\s I'm having are, what/which entity is causing this? 2) Has there been an official OBS response to this specific issue?

Respectfully
 

whitegold

New Member
This occurrence is still evident in 32.0.2 (64 bit). I've tried the workaround mentioned above which hasn't been effective. It seems to be an issue with the way a persistent stream key is managed.
 

kruseb

New Member
I see the same problem also. If someone has a fix for this, please reply. The suggested fix earlier does not work for me.
 
Top