This has become an issue since the integration of Microsoft Copilot into Edge Browser and Bing Search.
Try waiting up to 5 seconds (2-3 seconds if you're lucky) after entering your search terms and before hitting <ENTER> or <CR> - this seems to give the now "built-in" and utterly wretched AI / Copilot the time it needs to sidetrack your searches. and do it's "business" while allowing Rewards to register.
It should never take 24 hours for a simple 3-Rewards-Points-search to be awarded - never.
The root cause seems to be this (vile) imposition of AI, and - the modern equivalent of the obnoxious and patronising 'Paperclip' from earlier versions of Windows - the ultra-obnoxious MICROSOFT Copilot.
Since that time, when carrying out searches in Edge or Bing for Rewards, both AI and/or Copilot cause a lag or delay in the search process in Edge / Bing (on mobile, PC/Laptop and Xbox), as well as frequently causing Edge / Bing search to hang and freeze on searches, and resulting in earned Rewards points not being awarded.
If Rewards points are not recognised or not awarded for an individual search - despite no Rewards points being awarded for that search - that/those exact same search term/s will not attract Rewards points in the current 24 hour Rewards period - i.e. until after Rewards are reset at every 24 hours
I'm sure AI and even Copilot will improve over time but currently, Microsoft AI and it's Copilot within Edge are simply very irritating bloatware causing all searches to route for or through them, resulting in hiccups, lagging behaviour and missed Rewards.
Currently, for simple searches in particular, Copilot resembles a very curious and polite, yet supremely irritating 3 year old which insists on constantly interrupting to ask about every keystroke or search and offering (very slowly typed on screen) some unwanted and unhelpful rambling drivel which barely relates to your search terms and adds absolutely nothing to searches beyond simply being irritating.
Note: Disabling Copilot as much as possible in Edge / Bing does not resolve this issue.