It has to be on sometime between Oct 23rd and 30th. I was on vacation between these dates, so I don’t know exactly when it had happened, sorry.
All were created on the Org.
We have three users on our Atuin Desktop Org.
Coming back to it now, I’m not entirely sure about the one that still has the content but the title is “Untitled”. Maybe someone just forgot to add the title to that one. But for the other two “Untitled” ones under the “Test” folder, I know they both had content and at least one of them had a decent title. These two report their last update date is “4 days ago”. The entirely lost one was the one we were working on as two people recently. My colleague noticed that one got lost but he’s on vacation now. I’ll ask him when he found out it was gone and let you know.
The lost runbook in particular seems a lot like the issues we saw before we switched to the new workspace system in 0.0.106 or so, but if all the runbooks were originally created on the org, that seems unlikely.
We make backups of all your local databases when the app updates, so there’s a chance we have the runbook you’re looking for in a backup file. If you’re interested in recovering it, I can put something together.
It would be nice to have the option to have a local copy as atrb runbook files of the runbooks on the hub. This can be an export option, too.
One more thing I noticed:
My setup is: 1 personal (local) and 1 org (hub)
When just click the “+ New Runbook” button without explicitly clicking its dropdown to pinpoint the exact target workspace, it’s storing the newly created runbook on the previous place (hub or local).
Say I had created a runbook on the org. and swithced back to my personal space. When I click “+ New Runbook” the runbook is saved on the Org., not the personal space, even though it’s currently been switched to.
That also might have created a confusion with all that “Untitled” empty runbooks on the Org.