A 15-minute server cron only gives WordPress a chance to process its queue every 15 minutes, so a post scheduled just after a tick can be nearly 15 minutes late even when it’s working normally.
Use the browser Network log and an external header check together: the first shows whether the browser made a redirect request, while the second shows whether the redirect still exists outside that browser.
It’s usually a cache split: your logged-in request bypasses the public page cache, while logged-out visitors are still getting an older cached homepage.
That usually means Search Console is comparing two different snapshots: the Page indexing report remembers a crawl where the URL redirected, while the live test follows the redirect and tests the destination now.