Walsall "not expecting" ex-loan duo Jid Okeke and Ryan Finnigan to return
Mat Sadler says he does not expect former loan pair Jid Okeke and Ryan Finnigan to return to Walsall in January.
Okeke and Finnigan were recalled by Stockport County and Blackpool respectively at the start of the transfer window.
Finnigan has played just 17 minutes since returning to Blackpool and Okeke has totted up only nine minutes from his two cameos from the bench for Stockport.
Because both players have represented two clubs this season, meaning they are only eligible to re-join Walsall if they head out on loan again in the Football League.
But Sadler does not anticipate that either of them will be returning to Walsall before the winter window shuts on Monday next week.


"Ryan came on for Blackpool so I don't expect that to change from their perspective," boss Sadler revealed.
"He is in their squad now, so I don't expect him to come into ours.
"With Jid, I don't really know the lay of the land there. It's a little bit more complicated with Stockport and other things he might have in the future.
"I wouldn't expect to see either of them come back."
Finnigan scored four goals in 26 appearances for Walsall in all competitions - including three in League Two.
All three of his league strikes came in November when he was crowned League Two player of the month.
Okeke played 13 times in League Two and made a further 18 appearances across all competitions.
The German-born wing-back scored his only goal during his debut in a 3-1 win over Shrewsbury Town in the EFL Trophy in early September.
Dan Cox also saw his loan spell from Derby County cut short due to a lack of minutes on the same day as Okeke and Finnigan were recalled.
Since, Alex Pattison signed from Bradford City for an undisclosed fee and loan pair Kacper Lopata and Aaron Loupalo-Bi have arrived from Barnsley and Fulham under-21s respectively.
Comment Guidelines
Iconic Media encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.
