Release 1.3.11


  • Added a fix for a condition where your changes might stop getting saved to the database.
  • Added alerts to let you know when issues might be occurring.


A few customers reported leaving a scene and having words gone when they came back. This has been rare and I have not been able to reproduce it, but I believe I have now guarded against it.

Technical details: the only way I can see this could happen is if a receive-changes operation never completes, causing the changes you make (like writing text) to wait on that operation forever. I have set a timeout on the receive-changes operation so if it doesn’t complete normally it will error out, allowing your changes to continue being saved. It should also alert you there was trouble merging the changes.