Looking up the request ID, the issue is the same as reported here:
We are working on some bug fixes for this right now! In the meantime, as you’ve experienced, starting a new chat is the way to get around this issue. Hope we’ll have this fixed up for good soon.