“Schedule a Custom Event” will still run even after a “Go To Current Page” action. Technically this works because you’re not actually leaving the current page.
Good to use since an error pops up when the “Go To” action is not the last action in a WF.
I have a lot of UI that uses URL parameters and I need workflows to run after a UI change. For example, when a user wants to delete a record, a sidebar hides when a URL parameter is empty and then delete the record.
This is another nice benefit of how Bubble handles that go to page action when navigating to the same page the user is currently on. Thanks for sharing.
A couple of others are:
We can put conditions onto them to break the issue in the issue checker. I’ve done that in order to have more than one possible go to page action run from the same workflow series.
You can also wrap the “Go to page” action in a Custom Event and use it wherever you want in the sequence of actions, without the need for it to be the last action (as long as it is the last action within the Custom Event).
I usually try not to work around the “Go to Page” action error (or any Bubble errors for that matter). My thinking is that there should be a reason why Bubble considers it an error, and I don’t want to end up troubleshooting and realize a workaround failed 
Been there and boy oh boy… not worth the trouble.
I think it was an issue with the copy and pasting of “illegal” conditions into privacy rules.
