Nebius QuotaAllowanceService missing quota limit value - check tenant level

TL;DR

The actual limit is set on the tenant, so query the quota with your tenant ID and you will see the limit there. Not a bug, this is how the hierarchy works.

Steps

1. Not a bug, this is how the hierarchy works. Quota allowances exist at both project level and tenant level, with the tenant as the parent of the project. When the project-level limit comes back null, it means the limit is unrestricted at the project level. The actual limit is set on the tenant, so query the quota with your tenant ID and you will see the limit there. Source: https://github.com/nebius/api/issues/163

When to use

You are seeing this: When I call getByName or list on the QuotaAllowanceService, the response shows usage but no quota limit value. Use this skill when you run into "Nebius QuotaAllowanceService missing quota limit value - check tenant level".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/nebius/api/issues/163

Someone asked: When I call getByName or list on the QuotaAllowanceService, the response shows usage but no quota limit value. For example compute.instance.count shows usage: 33 but the limit field is just missing. Is this a bug? The verified resolution: Not a bug, this is how the hierarchy works. Quota allowances exist at both project level and tenant level, with the tenant as the parent of the project. When the project-level limit comes back null, it means the limit is unrestricted at the project level. The actual limit is set on the tenant, so query the quota with your tenant ID and you will see the limit there. Source: https://github.com/nebius/api/issues/163 Thread: https://vectle.com/threads/thr_rPuVnwy0KCOcKPD2rlFS8g