Hi,

For some reason this post was flagged as spam today. Not sure why someone would flag my post as spam. I’m a person, not a bot, lol. I’m new to this, and I’d appreciate some help from anyone with the time and knowledge. It was suggested by the automated system that I edit my original post so it doesn’t look like spam. Again, I don’t understand this. I’m keeping my post below as-is.

I have one private GitHub monorepo connected to five Vercel projects. Each Vercel project has its own Root Directory, and native Skip Unaffected Projects is enabled.

Most commits affect only one project. The normal result is:

• One affected project builds successfully
• Four unaffected projects appear as CANCELED
• The canceled projects show the native monorepo skip reason: skipping-unaffected-projects

After approximately 20 commits, I reached the Hobby deployment limit and GitHub showed all five Vercel checks failing with:

Deployment rate limited — retry in 24 hours

I inspected the repository and found no additional deployment triggers:

• No GitHub Actions deployment workflows
• No deploy hooks
• No automatic Vercel CLI deployment commands
• No Vercel API deployment calls
• No package lifecycle scripts that deploy

The commits that led to the limit changed files only inside one project’s Root Directory. They did not change root configuration files, shared dependencies, or the lockfile.

I received conflicting explanations:

1. I was initially told that all five records count toward the daily limit, including native unaffected-project skips.
2. I was later told that Skip Unaffected Projects should prevent those skipped projects from counting toward the deployment quota.

Could someone clarify:

1. Do deployments canceled with skipping-unaffected-projects count toward the Hobby limit of 100 deployments per 24 hours?
2. Should a native monorepo skip create a quota-counted deployment record?
3. Is there a way to see which deployment records were counted toward the limit?
4. Are there project settings that could cause all connected projects to consume deployment quota even when only one Root Directory changed?
5. Is there a supported way to ensure unrelated projects do not consume deployment quota?

I can provide redacted screenshots and deployment details if a Vercel team member needs them.

Thank you.