So if for instance on a search page we have a ‘Search’ button, that once clicked uses a workflow action ‘Go to search page’ and with this action we send the parameters to the exact same search page, then once the parameters are applied we’d want to refresh the page, so that its logged in Google Analytics. The issue is using the refresh action after the ‘Go to the x page’ creates an error, because of the ordering, unless a ‘Only when’ is specified, even though its the same page.
The workaround is to create 2 separate workflows on the button, 1 action for the ‘go to page’ and the other for ‘refresh page’, which I don’t think is recommend. Or use a constraint on the 1st workflow action, ‘Only when’ so it gets around the ordering last action error.
Example:

So just to summarise it would be nice if we could create an exception for the error that gets generated, if the ‘Go to page’ is the page in question (the page were working on), so that the ‘refresh the x page’ workflow can follow on and log as a new visit.
Cheers