A 302 redirect describes a temporary move. If the old page has moved permanently, that signal may no longer reflect the intention. Do not change the status solely because of its number, though.
Find out why the rule exists
Fictional example: during maintenance, /consultation/ temporarily pointed to a fallback page. After the relaunch, the same rule remains even though the replacement now lives permanently at /contact/consultation/.
Check the documentation and actual destination. Is the move final? Does the target contain the relevant content? Does another workflow still require the old URL?
For a permanent page move, 301 or 308 may be appropriate. The request method matters too. A form endpoint needs separate investigation and should not be treated like an ordinary page request.
Check the complete connection
Request the old address directly and record the status, target and any further steps. Then open the new URL without the redirect. Internal links and the sitemap should support the permanently chosen address.
A correct permanent redirect does not promise immediate adoption by Google or particular rankings. Record the change date and inspect the affected URLs in Search Console later. The decision that a move is permanent should follow the intended operation, rather than a blanket SEO recipe.
Related check: Prioritise a redirect mapping.
If old migration rules lack documented context, the Technology and stack review can help assess their place in the application.