title: IBM watson speech-to-text job hung in "processing" state
body: <p>I'm using <a href="https://stream.watsonplatform.net/speech-to-text/api/v1" rel="nofollow noreferrer">https://stream.watsonplatform.net/speech-to-text/api/v1</a> with mime type audio/mp3, communicating with async interface (http callback) on these events:</p>
  
  <pre><code>recognitions.failed
  recognitions.started
  recognitions.completed
  </code></pre>
  
  <p>Most of the jobs run well, but I've had one (e9be207c-348d-11e8-bd95-874f1d4b7552) that did this:</p>
  
  <ul>
  <li>2018-03-31/2:47:55: client started job</li>
  <li>2018-03-31/2:48:03: called back with "recognitions.started"</li>
  <li>2018-03-31/3:00:52: called back with "recognitions.completed"</li>
  <li>2018-03-31/3:00:52: client fetched job results, found state was still "processing"</li>
  </ul>
  
  <p>It's been in that state ever since. Audio attribs are ...</p>
  
  <pre><code>&gt; mediainfo ~/Downloads/11394.aud_watson.mp3
  General
  Complete name                            : /home/dougs/Downloads/11394.aud_watson.mp3
  Format                                   : MPEG Audio
  File size                                : 6.96 MiB
  Overall bit rate mode                    : Variable
  Writing library                          : Lavf56.40.101
  
  Audio
  Format                                   : MPEG Audio
  Format version                           : Version 1
  Format profile                           : Layer 3
  Bit rate mode                            : Variable
  Channel(s)                               : 1 channel
  Sampling rate                            : 44.1 KHz
  Compression mode                         : Lossy
  Stream size                              : 6.96 MiB (100%)
  </code></pre>
  
  <p>... with duration 12 min 15 secs.</p>
  
  <p>Any suggestions regarding how to diagnose what's happening on the watson server?</p>