Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Recognise the one use node
A developer loads a short audio cue, presses Play successfully, then finds that Replay throws an InvalidStateError. The AudioBufferSourceNode start documentation gives a concrete explanation: start can be called only once during that node lifetime. The cached audio data and the source node are different objects with different reuse rules. A successful first playback followed by this error is not evidence that the audio file disappeared or the network connection expired.
Keep scheduling and content offsets separate
The method also distinguishes when playback should start on the audio context clock from the offset into the audio buffer. For an illustrative exercise, scheduling a cue two seconds from now and beginning at its three second content position are different choices. Record both explicitly when an application appears to begin at an unexpected point. A buffer offset remains a source position even if playback is running at a different rate.
Repair the control lifecycle
For each Replay action, create and connect a fresh source node using the already decoded buffer when appropriate. Keep cancellation and finishing state attached to that new instance rather than a stale earlier node. Test a sequence of Play, finish and Replay with the same harmless local cue. That checks the actual interaction which previously failed. It does not require refetching the entire file for every button press, nor does it establish that a remote streaming account has been restarted or reactivated.