when we are using the {site} option sometimes the page has not been loaded in full and we may get an error , it would be awesome and really good instead of closing the snippet and opening again, instead an option to refresh the template that also allows it to read all information again to avoid this
Thank you for your feedback @Aldo_Barahona
Currently we have no plans for this, but this is a good idea and we will consider supporting it. Does it work for you if we just support refreshing the template window using Ctrl+R (Cmd+R on macOS)?
hi thank you for your promt response 
i work for an organization so i am not allowed to use some tools, but this is what i got if i use the crtl + r
Yes you see the blank page because Ctrl+R is not implemented yet. We'll update this thread when we plan to support it.
sounds good, thanks
As a direct solution to your problem, maybe there is a way to find out if a page has been fully loaded?
For the browser itself, it knows and can trigger an onLoad JavaScript event. Maybe TB can hook into that, given that it can 'see into' all pages?
As an alternative as a user, maybe you could determine something on a page that indicates it is done loading and implement something like a "while [ not fully loaded ] wait a second; repeat"?
(there is an IF switch; you could use that to keep triggering the same snippet until the page is loaded and only then continue executing)
Hi, was Ctrl+R ever implemented? I tried to use this with a snippet and got the same error as Aldo.
Hi @dallas we didn't Ctrl+R just yet. We'd love to hear about more use cases. Aldo's use case was to specifically refresh the {site} command values in the snippet. Do you have the same use case? If not, can you clarify yours as well?
Most of my organization's snippets include a series of dropdown menus that, when all of the selections are made, populate a specific email. Sometimes, someone will make a couple of selections, realize they made an error with the first one, and then go back to the first one to make a different selection. The issue, though, is that the selections in the other dropdown menus don't automatically revert to the default status. They stay stuck on the selected option, which can cause issues with the if logic as some of these menus don't appear again if the first selection is different. An option to refresh a snippet quickly, instead of canceling and rerunning it or going back through all of the dropdown menus one by one, would be more convenient.
I hope that makes sense! Let me know if you have any questions!
Thanks, Dallas, that's very detailed and makes sense.
For the moment, as a workaround, you can add a {button} to your snippet that resets each variable to its default state: Text Blaze | Buttons and Interactive Interfaces
Thank you for the workaround suggestion! It seems to be working in our initial testing.