@YounesGa To have each thread use only 1 line, set the value "max success usage: 1", "max number of simultaneous use: 1".
This is equivalent to the fact that after the flow finishes running with a result of Success, the already used proxy line will not be used again, whereas if there is an error, it will be reused 999999999 times and only one line. for each stream
290a12f6-98cf-4378-9d4c-72a246339adb-image.png
v25.3.0 Bug: Data Manager in Database shows correct total number of items, but empty items
-
Hi,
I found a bug on the databases of v25.3.0.
When the data in the database is more than 98 entries, the data manager shows the correct total number of items, but all the entries are empty.
The database manager also crashes if you then try to refresh the data.This is using a remote connection to mongodb by the way.
For example, here is a screenshot of what is happening:
There are 106 entries and the data manager correctly identifies that total. But then there are 106 empty lines.
If I try to edit an entry or refresh the data, the data manager crashes.
If I then delete 8 entries in my mongodb database, all the entries show up in the data manager and it works perfectlyCan you please fix this?
-
@js654 said in v25.3.0 Bug: Data Manager in Database shows correct total number of items, but empty items:
Hi,
I found a bug on the databases of v25.3.0.
When the data in the database is more than 98 entries, the data manager shows the correct total number of items, but all the entries are empty.
The database manager also crashes if you then try to refresh the data.This is using a remote connection to mongodb by the way.
For example, here is a screenshot of what is happening:
There are 106 entries and the data manager correctly identifies that total. But then there are 106 empty lines.
If I try to edit an entry or refresh the data, the data manager crashes.
If I then delete 8 entries in my mongodb database, all the entries show up in the data manager and it works perfectlyCan you please fix this?
This problem was found a long time ago, it can only be solved by updating mongodb. But since this is only a problem of displaying data in the data manager (getting data in the script is performed correctly), then this task has a priority lower than the current tasks.
