We ran to the same issue multiple times. However, I noticed later that the issue is more repetitive when the venv location is outside the reach of your workspace base directory or too deep inside the sub folders. So I suggest putting your python venv in the main directory where is your workspace opened. Then restart the VSCode if it doesn't run it.