The chatbot frequently stops responding entirely

[fagiothree]

Information we have on the issue:

• Wenhao managed to 'fix' the issue by resetting it to a previous state when it was functioning well. However, this does not solve the problem fundamentally. (TO CHECK WITH ZUYI: which state?)
• The problem is occurring more frequently
• Each reviewing session is becoming shorter and shorter, lasting no more than one hour
• It does not happen to a particular type of flow, and we find it completely random.
• We thought it might be because we did not respond in time and it timed out so we tried to avoid that, but it did not help
• Some screenshots from when the issue occurred not responding to any trigger

[fagiothree]

The rapidpro workspace had run out of credits and was is no longer processing messages. This explains why the chatbot has stopped responding completely from the 4th of January. The 'Test' organisation has now been topped up with credits, from 1000 to 10 million, with an expiry date 10 years ahead. This should eliminate the credit issue for the foreseeable future General administrator privileges have been given to Chiara, Ed and Wanhao, to empower them to perform more actions on the server (like top-ups). We believe that missing credits may also be the explanation for the unresponsiveness experienced prior to the 4th of January. In fact, it could be that the workspace ran out of credits earlier, and that when Wenhao was restoring everything to a previous point in time, the number of credits used was also being restored.