Thank you for the fast reply! I removed the aws pathway as suggested, but the error remains. I've validated the playlists and verified that I can play the media from both the azure and edge CDNs. In fact, I can switch between the CDNs using content steering as long as both pathway ids are specified in the manifest. For example, using manifest #EXTM3U #EXT-X-CONTENT-STEERING:SERVER-URI=https://example.com/content-steering?switching=true,PATHWAY-ID=azure #EXT-X-STREAM-INF:BANDWIDTH=5605600,RESOLUTION=416x240,CODECS=avc1.64001e,mp4a.40.2,PATHWAY-ID=azure https://azure.com/contentsteering/stream_0/stream.m3u8 #EXT-X-STREAM-INF:BANDWIDTH=5605600,RESOLUTION=416x240,CODECS=avc1.64001e,mp4a.40.2,PATHWAY-ID=edge https://edge.com/contentsteering/stream_0/stream.m3u8 and steering manifest { VERSION: 1, TTL: 10, RELOAD-URI: https://example.com/content-steering?&switching=true, PATHWAY-PRIORITY: [ edge, azure, aws ], PATHWAY-CLONES: [] } (It works with and without aws in the priority list, even thoug