I’ve noticed that console.log() has stopped working again in scripts and neither logs to the browser console nor the Activity log. This is such a useful debugging tool for scripts and markdown templates. Could we bring it back?
Buttons or rules?
Browser? OS?
1 Like
Apologies, should have been more clear. I was actually using it in a Button on Windows (confirmed in the app and Chrome). However, I was trying to use it within a script block in markdown template action.
Based on your question, I did a quick check and it works fine if I use a standalone Script action.
Does this mean if you include console.log() in a markdown template it won’t work? I seem to recall it worked in that context too, but I could be misremembering.
It never worked like that, so I suggest converting this to a feature request rather than a bug report.
1 Like
Thanks @Chr1sG I ended up just going with Script action which takes a bit more effort to setup but is probably much easier to read. However, having this ability would still be useful for some more complicated markdown templates.