There may be errors on the page. Did you check the browser console (F12 in Chrome) to look for errors there?
I’ve had the same situation on a couple of occasions and each time it was related to access rights. Are the FileDocument and the relevant assocations to and from it accessible for the users? I.e. in your case your will need at least read access from ‘Customer’ to ‘Request’ and (potentially) also from ‘Request’ to ‘Customer’
And of course read access to all attributes of the ‘Request’ entity.
There are a few things here I will try my best to explain.
Your retrieve for 'CustomerRequest_info' is not necessary and will always be empty as you are retrieving over an association from the created Customer_Request document but your create action has not set any association. You can remove your CR_Info action as you are correct it is not being used.
I think what you mean to do is not retrieve but set an association. You say in the create action you are referencing to the order/CustomerRequest within the 'entity' input box but this is incorrect, you are not setting a reference/association here. You are creating an object of 'CustomerResquest_Document', which is a single entity in your Domain Model; not setting a reference between a CustomerRequest and a Document. To set this, in your CR_Document object add a new member setting the association to your from CustomerRequest parameter.
Then in your second microflow you retrieve the CR_Document from the database but this will always be empty as you did not commit it in the first microflow. Changes will only be made to the database with a commit. So you should add a commit action at the end after the PDF generation.
You would now have a customer request parameter, create a CR_Document and associate it to this, generate the PDF, and commit it.
In the second microflow you might also want to change things so it's not just retrieving the first entry in the database as if this logic were used in Production you'd have no idea if the first entry is related to the CustomerRequest parameter or not.
So your retrieve ought to be over the new association created in the first MF. Alternatively set an output on your first microflow to be the $CR_Document object and then in your second MF in the sub-MF action enable using the output variable, so you can then pass this directly to the download without using a retrieve