Journal items missing

UPDATE This issue has been resolved. Please see full post below. <a href="https://app.roll20.net/forum/post/11977191/journal-items-missing/?pageforid=11978102#post-11978102" rel="nofollow">https://app.roll20.net/forum/post/11977191/journal-items-missing/?pageforid=11978102#post-11978102</a> The post below has been edited to reflect more accurate information. Hey folks! Really sorry to hear that this issue is happening! We've been investigating affected games and our discoveries have pointed to majority of these issues being caused by a 3rd Party extension. CLARIFICATION: This issue in particular was not caused by an extension, but rather more likely to encounter and trigger the root cause due to extension behavior. Extensions in general are not advised to be enabled while using Roll20. They can interfere with performance at best and corrupt or destroy game data at worst. If you are encountering this issue, we can take a look, just reach out to Roll20.net/help and our support team may be able to assist further. For those who have a Pro subscription, we advise making a copy of the game and then performing a Rollback in order to recover any lost information or organization.

Hey everyone, I wanted to come back to this with an update on this situation with what should be some good news-- We've located the root cause of this issue and a fix should be live now. Some important information first: If you were impacted by this problem (i.e. folder structure broke) please reach out as soon as possible to help.roll20.net to send in a support ticket and our staff will assist. Rollbacks only go back 7 days so beyond that we may not be able to assist. Due to the nature of this issue and the fact it impacted journals, this fix is not retroactive If you are a Pro user you can already use the Rollback tool. I recommend making a copy of the game first then performing a rollback on the affected game. Rollbacks are not a guaranteed fix. Some games may be too large for the rollback tool to function. Our support team will continue to try to assist, but this is primarily due to hard limits by Firebase and is out of our control at this point in time. Now for some more details. This issue was a doozy. The extension aspect of this problem as we found with more reports was a red herring. So I want to extend my apologies for any confusion on that matter this may have caused.&nbsp; I will reiterate that extensions are not recommended at this time because they can cause issues that we are unable to resolve and can introduce performance or data problems in games. This particular issue was difficult to replicate as the requirements are very system and time dependent. This was to such an extent that extensions were actually perfectly positioned to reliably trigger this issue due to the speed at which they operate. However, thanks to the follow up reports and information provided here and by those who wrote in we were able to discern that our initial hypothesis was incorrect and we began working towards finding that root cause. We will be following up shortly with those who have already written in to inform on the situation and provide an update in addition to assisting with Rollbacks where necessary. Thank you again everyone, genuinely, for continuing to raise your concerns and voice the issues you were facing. This information and that submitted via support tickets is absolutely vital for us to track down these tough issues and get them fixed quickly. Again if you were impacted by this issue, please contact our support team at help.roll20.net so we can help get you taken care of quickly!