@Amar-Azure-Practice If your sender application is sending the message to the queue (session enabled) using session ID then your receiver application will only be able to receive the message if the session ID is passed while making the receive call.
You need to pass your custom session ID (same when you are sending the message to queue) or next available session ID option in the Session id dropdown. In the below screenshot I have used the session as "Next Available".
Hope the issue resolved after updating the session ID from the drop down. If you are still facing the issue please share the exception message when you are running the trigger manually.
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.