When a guided report that needs a run time parameter is executed it works fine, but if the results are presented in more than one page, clicking either a page number or the 'next page' link (>) executes the report as if it was the first time. It asks for the run time parameter again and presents the first page of results.
Tests show that this is fixed adding 'sql_param=[runtime parameter here]' to the link to the other results pages.
I tested this on current master and paging works with runtime parameters without problems there. The bug was filed against 3.2 which is no longer maintained. Marking WONTFIX.