Activate() breaks Automations

Hi all,

I found a bug that is (I hope) easy to fix!

If you use Activate() in a button and then run the button in an automation, it throws an error saying that UI actions can’t be run on the server. The expected behavior would be that Activate() should be a no-op on the server and the button should still run, since the activation makes no difference to the impact on the doc state.

In the meantime, I’ve removed Activate() from our buttons and created a second button that activates after the other button is run.