Dependabot is not creating PR

We have multiple .net repos. I have setup dependabot in one of my repo, it works as expected. But I’m facing problem with another repo.

This repo has multiple solution files and different folder structure. We have defined all the nuget and other private packages in the central package management file Directory.Packages.props. The Directory.Packages.props file and solution files are not in the same folders in this case.
I’m suspecting that this is the main reason for not working. So can you tell me if there is a way to support this or is it mandatory to have the solution files and Directory.Packages.props file in the same folder. I think should be a way to fix it. I have also tried setting the directory to src, but it also didn’t work.

Folder structure:

src/Directory.Packages.props
src/solution1/solution1.sln
src/solution2/solution2.sln

Dependabot yml file

version: 2
updates:
# --- Main workflow (DO NOT REMOVE) ---
- package-ecosystem: "nuget"
directory: "/"
schedule:
interval: "daily"
time: "18:30"
timezone: "Asia/Kolkata"
open-pull-requests-limit: 5
target-branch: "master" # Default branch
registries:
- nuget-org
- uno
- devops
- engines
- security
groups:
all-dependencies:
patterns:
- "*"
ignore:
- dependency-name: "*"
update-types: ["version-update:semver-major"]

# --- TEMPORARY for testing only ---
- package-ecosystem: "nuget"
directory: "/"
schedule:
interval: "daily"
time: "08:00"
timezone: "Asia/Kolkata"
open-pull-requests-limit: 2
target-branch: "vitara/test-dependabot" # Test feature branch
registries:
- nuget-org
- uno
- devops
- engines
- security
groups:
all-dependencies:
patterns:
- "*"
ignore:
- dependency-name: "*"
update-types: ["version-update:semver-major"]

registries:
nuget-org:
type: nuget-feed
url: "https://api.nuget.org/v3/index.json"

Reproduce the NuGet update with the reported layout: src/Directory.Packages.props, src/solution1/solution1.sln, and src/solution2/solution2.sln, using the shown dependabot.yml entries for directory "/" and "/src". Start by checking how Dependabot discovers Directory.Packages.props relative to solution files. Done means the configuration is either supported with a documented setup or the limitation is clearly identified.

Written by the indexing model from the issue text.