Ignored following counts as processed

[zoltan66]

Hi Martin,

I have this problem for as long as I can remember, my accounts hardly follow anyone a day because (i think) twitterdub also adds the ignored follows to the total number of accounts to be followed.

Here is an example to understand my problem a bit better:
I make a following proccess to follow 40 accounts, but twitterdub ignores 35 accounts because they have been processed before or have a filter etc. but when the process is finnished it says: Processed: 5/40 Failed: 0
Ofcourse If possible I want TD to actually follow 40 people and not count the ingnored accounts.


Here is are some of my logs, but if you want I can send all the logs.


Process: 40/45 : https://twitter.com/KassemOtako
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/KassemOtako
Process: 41/45 : https://twitter.com/6MjzyuIbVgIOTZF
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/6MjzyuIbVgIOTZF
Process: 42/45 : https://twitter.com/xRQcc3jErLasGcb
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/xRQcc3jErLasGcb
Process: 43/45 : https://twitter.com/johnnybravoo666
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/johnnybravoo666
Process: 44/45 : https://twitter.com/badbitchesonlym
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/badbitchesonlym
Process: 45/45 : https://twitter.com/hxhqxquwu
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/hxhqxquwu
All items: 45
Remaining items: 44

*********
Processed: 1/45
Failed: 0

[BAWZ]

Strangely, this looks like the exact same thing I asked not 30 mins ago! See the post below this one

[zoltan66]

Strangely, this looks like the exact same thing I asked not 30 mins ago! See the post below this one

Wow indeed, I didn't see your post before posting this, that's some strange coincidence as I have had this problem for a long time and just decided that today I will address this on the forum.

[BAWZ]

Me too!!

[martin@rootjazz]

Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/6MjzyuIbVgIOTZF
Process: 42/45 : https://twitter.com/xRQcc3jErLasGcb
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38
* IGNORE: https://twitter.com/xRQcc3jErLasGcb
Process: 43/45 : https://twitter.com/johnnybravoo666
Selected account: ***********
*********** processed: 1/0 (MaxPerAccount)
Use account: ***********
Loading previous db logs: ***********_Follow
*********** Loaded previous db logs: 169122 processed: 9840 within 24hrs: 7
0/1
Global Daily limit: 38
Daily limit: follow for account: *********** 7/38

IGNORED items are not added to the daily amount, look at the bolded above, it shows 7 of the 38 limit processed... So that isn't the issue

[martin@rootjazz]

when the process is finnished it says: Processed: 5/40 Failed: 0
Ofcourse If possible I want TD to actually follow 40 people and not count the ingnored accounts.

ok so the program does have a known issue, it's by design really, but the program:

Step1: scrapes + filters to get your (total)
step2: Then it processes the (total)

Items shouldn't really be ignored durining step2, they should be ignored during step1.


The question becomes, why are they being ignored? Well if the program doesn' tknow it has follow the accounts before, then when it gets to actually following them, yes it could lead to ignoring the item. But this shouldn't really happen alot, Unless you removed the database / deleted / re-added the account with new database ID.

[martin@rootjazz]

so question becomes, WHY are they ignored. Unfortunately logs do not say. I'll need to improve the logging to state why item ignored.

Can you just explain how you run your action so I can try adn replicate it. Whether it's a search or a prepared list of items to follow or...

[zoltan66]

so question becomes, WHY are they ignored. Unfortunately logs do not say. I'll need to improve the logging to state why item ignored.

Can you just explain how you run your action so I can try adn replicate it. Whether it's a search or a prepared list of items to follow or...

I also have to tell you that when I start up a brand new account this issue does not occur in the beginning, it starts to occur over time or if it's set on the global logs where other accounts have gathered data on.

This is how I make a follow process: I gather all the big Twitter accounts where I need the followers of in a notepad file, then in the program, I go to multisearch and paste the notepad file path in the search bar, I change "num results" and "fluctuate". In options, I add FollowersOf and click add. then I also mark "process single search per action I click ok and close multisearch. Then I click "daily run at" and let it run everyday at midnight with a flux of 300. random pauze 45-300.
If it is a new account I sometimes merge that account with the other accounts and put them on the same global logs. (If I don't merge and put them on the existing global logs then the following problem does not occur in the beginning as said above) Then I click "follow" to make the action.
Also interesting to know I'm not sure if this is normal or I'm doing something wrong but this method creates for every account that is listed in the notepad an extra action. So if there is 20 accounts in the notepad that will create 20 follow actions, I think this is something that didn't happen in the beginning I was using this method but anyway what I do is just delete 19 of the 20 actions so I have 1 left.

[martin@rootjazz]

so question becomes, WHY are they ignored. Unfortunately logs do not say. I'll need to improve the logging to state why item ignored.

Can you just explain how you run your action so I can try adn replicate it. Whether it's a search or a prepared list of items to follow or...

I also have to tell you that when I start up a brand new account this issue does not occur in the beginning, it starts to occur over time or if it's set on the global logs where other accounts have gathered data on.

ok, so if it happens after time, then it sounds like the database is out of sync for whatever reason.

shared action, might explain it, if the action performing the search hasn't processed the item, but the accounts selected to do the follow, I Suppose that could happen, however, the program should be using the records of ALL accounts for the search, not just the account performing the search. I will need to confirm this is working, as perhaps when searches updated the code was missed off... that might explain it.

I will need run tests and get back to you

[zoltan66]

I also have a problem in some instances with loading the global logs,I wanted to open another post for this but perhaps they are correlated?
If I put my account on a global log a new one or an existing one they get errors, it only happens in a few of my instances and I have no clue why. Here's what happens if I run a follow task on an account that has global logs:



Starting: 04/03/2023 14:16 pm
Processing: Multi Search Builder: 18
Loading previous db logs: "Myaccount"_Follow

*********
Processed: 0/0
Failed: 0
*********

* ERROR: CRITICAL_93785439537530: Previous processed logs failed to load - please contact support and submit logs for review: global_all C:\Users\dimit\AppData\Roaming\rootjazz\Twitterdubbichild\database\DbLoggedData\global_all.bin
* UNKNOWN ERROR OCCURRED:CRITICAL_93785439537530: Previous processed logs failed to load - please contact support and submit logs for review: global_all C:\Users\dimit\AppData\Roaming\rootjazz\Twitterdubbichild\database\DbLoggedData\global_all.bin - see logs for more info.
If the problem continues, please submit logs to support.

HELP > LOGS > SUBMIT
then write an email to support@rootjazz.com and include your logs ID - the numbers are sufficient (displayed after successful uploading of logs) and any other information regarding the error

CRITICAL_93785439537530: Previous processed logs failed to load - please contact support and submit logs for review: global_all C:\Users\dimit\AppData\Roaming\rootjazz\Twitterdubbichild\database\DbLoggedData\global_all.bin

loc:1687684568
Repeat action: daily runner: 0:0
Repeat action: hours: 0 mins: 0
loc:16488614786718676878647
Fluctuate wait: 300
Random fluctuate: 300
Next Daily runnner: After Fluctuated: 2023-03-05 00:43 am
Repeat action: schedule time: 05/03/2023 00:43 am
Scheduled to: March 05 2023 00:43 am
Action completed as Run in Additional Thread - removing thread