Templated Macros Not showing in Chat Archive!

I am getting this error again after it some what cleared up but it's back to none of the templated macros showing in the chat archive! Even newly created templated macros do not show!

A game's creator is often able to fix issues with their Text Chat by clearing the Chat Archive (note: not clearing your current Chat Log ). A GM might want to copy/back up the Chat Archive before the creator clears it.

I clear my chat archive every week by the start of the next session!!!!!!!!!!!!!

I'm telling you guys there really is a glitch somewhere! I edit down my chat archive each week to make a story chapter and the combat part is basically missing because the templates will not show in the chat archive!

Then you're ready for the next troubleshooting step:  Would you please carefully work through the first three steps of our guide to Solving Technical Issues ? Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome and Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable all add-ons/extensions and anti-virus programs. Step 3: Clear your cache If none of the above succeeds, please thoroughly work through Step 4 . (Don't forget the complete Console Log, starting from table loadin through using a few of the templates that don't show in your archive, AND then including when you try to look at the archive and see that the templtes aren't showing!) Please be aware that the Devs will be on vacation from the 9ths through the 12th, so if you reach the console log stage there may be a delay in getting help at that point. Thanks!

It appears to have cleared up late last night when I tried some templated spell macros. They showed in the chat archive and appeared after I copy / pasted them into a word processor. I have tried all those above steps before and and did not clear up! I'll see what happens tonight after the game session.

If steps 1 through 3 didn't fix anything, we'd need step 4 for the Devs to poke at.  Step 4 doesn't 'fix' anything on its own :)