I knew this would happen when I implemented cycling; what's happening is that the cycler is stopping some other animation (most likely typing) that populated the 'current animation' state. (The code is not fully intelligent about multiple animation layers.) At the time I felt it was an acceptable defect that would only trigger in fairly obscure situations, but it seems you've caught me on that corner-cutting. Limiting the behavior of NanAO's cycling to only consider stand animations, and to understand them a bit better, should deal with this.