does not transfer the user to limit status when he has spent it

[DDjakes]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Set limit user 0.5 gb
2. Use traffic for limit

Expected behavior
A clear and concise description of what you expected to happen.

Set status limited for user

Screenshots
If applicable, add screenshots to help explain your problem.

Machine details (please complete the following information):

• OS: [e.g. ubuntu 20]
• Python version: [e.g 3.8]
• Nodejs version: [e.g 16.17]
• Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

The user has a traffic limit of 0.5gb, marzban successfully counts the spent traffic, but when the traffic reaches more than 0.5gb, marzban does not transfer the user to limited status, thereby the user can continue to use the config, up to an endless waste of gigabytes. This problem appeared after I exceeded 350k configs in the panel.

[ImMohammad20000]

I test this and there is no problem!!

[DDjakes]

These are the last entries, not taking into account that yesterday I already cleared 57 thousand entries for this condition

[ImMohammad20000]

Do you use dev version?

[DDjakes]

Do you use dev version?

I'm using release version 0.7.0

I also do not see any errors in the output of marzban logs

[ImMohammad20000]

Send a screenshot from panel

[DDjakes]

Send a screenshot from panel

[DDjakes]

marzban_1 | Execution of job "review (trigger: interval[0:00:10], next run at: 2024-12-30 12:00:23 UTC)" skipped: maximum number of running instances reached (1)

I get this message in the logs, I looked at the code of this cron task and saw that it does exactly what I need, namely checks and issues statuses. How to make this work?

[M03ED]

this is because you have 350k active users and checking this much user will take a long time, (more than few minutes)

[DDjakes]

это потому, что у вас 350 тыс. активных пользователей, и проверка такого количества пользователей займет много времени (больше нескольких минут)

More than a few hours have passed since the last request to verify incorrect users, and their number has only increased. That is, I am now observing that status = limited is not issued to anyone at all.