Promo Module Doesn't Follow or Unfollow

[omegasolutions]

Neither account that I manage unfollows...who knows how long it's been like that this. Just checked today's log and yesterday.

Code: Select all

Starting: 24/08/2017 06:46 AM
Search: 
Num: 150
Unique: False
SearchType: -1

Processing:  max: 150
*** Pre Search Setup***
Loading previous db logs: 447969d9-4c03-4aef-b562-ad2a8aaee987_Unfollow
Loaded previous db logs: 0 processed: 0 within 24hrs: 0
*** Performing Search ***
Unfollow only bot follows
Loading previous db logs: 447969d9-4c03-4aef-b562-ad2a8aaee987_Unfollow
Loaded previous db logs: 0 processed: 0 within 24hrs: 0
Found: 0
Loading previous db logs: 447969d9-4c03-4aef-b562-ad2a8aaee987_Unfollow
Loaded previous db logs: 0 processed: 0 within 24hrs: 0
Started: 24/08/2017 06:46 AM
Finished: 24/08/2017 06:46 AM
ID: 043c8a10-12dd-4a62-8b05-aa7dc0cf0f84
Action ran for: 0hr:0min:0s
Repeat every: 24
Run Next: 8/25/2017 6:46 AM
Fluctuate wait: 60
Random fluctuate: 60
Run Next: After Fluctuated8/25/2017 6:06 AM
Scheduled to: 8/25/2017 6:06 AM

They both do this

Logs: 39700

[martin@rootjazz]

it appears that the program cannot find your bot follows.

I cannot see any normal search and follow actions in your logs (have you run any previously?) but I do see PROMO FOLLOW actions. These should be found by the program to unfollow, but do not appear to be detected. I am checking on this now and shall get back to you shortly

[omegasolutions]

Correct. I am using the promo follow/unfollow.


It is following no problem, just not unfollowing.

Thought you said twitterdub didnt have a promo
(Or maybe you meant its not as detailed as instadub)

[martin@rootjazz]

promo follows working fine for me being detected for unfollows. So it isn't promo follows incorrectly recorded.

let me check on promo unfollows didn't realise you were using that for unfollows

Thought you said twitterdub didnt have a promo
(Or maybe you meant its not as detailed as instadub)

I thought you meant the same kind of promo module, the TD promo is what instadub used to have, just create actions for you. Whereas the new one is a perma-action self contained in a single thread.

[martin@rootjazz]

Anyway, I cannot find out anything as to why it cannot detect them

Can you zip your database folder and send it to me

%appdata%\rootjazz\twitterdub\

If it is large, please upload it to a file sharing site: dropbox / drive / sendspace etc



Regards,
Martin

[omegasolutions]

I thought you meant the same kind of promo module, the TD promo is what instadub used to have, just create actions for you. Whereas the new one is a perma-action self contained in a single thread.

I understand what you mean. Based on that info, I actually created an unfollow action (outside of the promo module) and it unfollowed.

And the database was sent.(before that action was created)

Edit: The promo module just isn't working. I'm supposed to be following 150 every 24 hours. It hasn't done that in a week, even if I was to add all the days together.

2nd Edit: Side note; you can see where I created that unfollow module outside of promo on the 25th. So, yeeea....

[martin@rootjazz]

the unfollow promo routine will not start to unfollow bot follows until after 7 days. For me, this is working correctly. I have added additional logging to show what is happening.


As to your not hit daily limits for follows, I'd need to see logs showing this

[martin@rootjazz]

actually I already have teh logs, let me check those

[omegasolutions]

As to your not hit daily limits for follows, I'd need to see logs showing this

It should be in the logs I sent previously; Logs: 39700. Since they have never met limits.

Code: Select all

Loading previous db logs: 447969d9-4c03-4aef-b562-ad2a8aaee987_Follow
Loaded previous db logs: 360 processed: 360 within 24hrs: 21
[b]Daily limit for account: 150 - processed: 21[/b]
Processing: 4358034628 with user: xxxxxxxxx
Using acc: xxxxxx on: 4358034628
Get TwitterUser: 4358034628 using: xxxxx
Follow: 4358034628 using: xxxxxxxx
logging processed: 4358034628
* SUCCESS (22): 4358034628 user: xxxxxxx
Check for pause: 90,180
Pausing for: 178
Paused for: 178 seconds
Processed all items
Started: 25/08/2017 19:17 PM
[b]Finished[/b]: 25/08/2017 21:14 PM

[martin@rootjazz]

ok, so sometimes you hit the limits and some times not. It seems that the removal of already processed items is happening after the scrape. So scrape works out you need 150 items to hit limit, returns 150, THEN it removes already processed, leaving you just 40 items, this should happen during the search.

Checking that out and will push an update to fix it shortly