fail early actions / failed to authorise

[martin@rootjazz]

The main problem I want to focus on is the failing & early completion of "Like, follow, retweet" actions. There seems to be 2 scenarios. 1. I start my accounts doing any of the follow actions above, the first 10 or so work (no matter what first 10 are selected) and then after that it starts throwing the object cant be located error mentioned above.

OR 2: it says that the account can't be authorized and then fails. I will then re-authorize the account and it will work for another 16-20 hours before needing to be reauthorized again. There's doesn't seem to be any reasoning to the accounts which need it, it seems to randomly pick through them.

I'm also running fairly conservative amounts of actions per account (or at least I'd like to think I am).

I am trying to re-update the program now and I will get back to you Mr. Martin. Sorry I get a tad bit frustrated. I am paying for proxies and buying accounts and all that good stuff so I have a bit invested in this as well. That was the only reason I was getting frustrated, I feel like I take 1 step forward and 2 steps back haha. I can never seem to get the program to run @ 100% for longer than 18 hours without throwing failures.

I am trying something new though as well with tweet stream and all that good stuff. I will keep you updated. Thanks for your patience and time. I hope you have a happy new years man. I'd share a Guinness with ya if I could.

Talk soon!

[martin@rootjazz]

The main problem I want to focus on is the failing & early completion of "Like, follow, retweet" actions. There seems to be 2 scenarios. 1. I start my accounts doing any of the follow actions above, the first 10 or so work (no matter what first 10 are selected) and then after that it starts throwing the object cant be located error mentioned above.

please confirm these are
1) shared actions
2) 10+ accounts
3) what search? custom / normal (from drop down)
4) filters?
5) other parameters


Do I have a log of this? If so, can you resend the logid, or:



Please perform the following:

delete existing logs
HELP > LOGS > VIEW
delete all files in the folder that opens


Perform the action:
***
run the action as detailed above

when starts to fail, let it complete or cancel
***

PLEASE NOTE: Do not perform other actions at the same time. Only use one thread. Do not run any actions after this action.


Then submit logs:
HELP > LOGS > SUBMIT

and let me know the LOGS ID (just the number part is sufficient)

[martin@rootjazz]

OR 2: it says that the account can't be authorized and then fails. I will then re-authorize the account and it will work for another 16-20 hours before needing to be reauthorized again. There's doesn't seem to be any reasoning to the accounts which need it, it seems to randomly pick through them.

What is the search for this? I have noticed something similar myself, but it occurred when I performed an illegal search.

say "scrape followers of" and I provided a term of "#soundcloud" which of course isn't a user. Twitter responded with "unauthorised user". Which is confusing as that is not the issue, the issue is "invalid term", but that is how twitter respond. As I detect these, I update the program to try and return a better error than given by twitter, but it basically relies on me hitting the issue then adding a check retroactively, there is all but an unlimited number of errorous terms that could be provided so pre-emptively guessing them is hard.


But this does not sound like your issue exactly, but it could be that twitter responds with that error ALTHOUGH the actual cause is something else.


So in the spirit of going back to the start to ensure I haven't missed anything, what actions cause these?
Shared?
Filters?
Options
Search type? Search term

When the issue occurs. If you just wait an hour, then run a test action
mass follow X profile with a single account

what happens?

[TwitterNub]

working on getting you these now. I will send you the logs within a few hours. Thanks Martin.

[TwitterNub]

OK, I went ahead and performed a like action with 11 of my working accounts (leaving the 2 accounts that went "null" out of the equation).

Logs #: 55553

Settings were as follows.

single search term "nsfw" and search type is "Tweet search" or "authors returned by tweet search".

30 actions per account, all other settings were left default.

Screen shot of settings: http://imgur.com/4NygCI4

I will now try a set of the same actions with the same accounts iwth "uniques only" unchecked

[TwitterNub]

Same settings used as above, same accounts, same search term, only difference is I unchecked "Unique only" which is normally checked by default.

screenshot of settings: http://imgur.com/0uVmGtG

Logs number: 23986

Did the exact same thing really, I haven't looked through them but my first account didn't get any likes which is a bad sign for the rest

[martin@rootjazz]

the location your logs indicate as the cause, should be able to handle whatever is happening now. Will post update shortly

[martin@rootjazz]

the location your logs indicate as the cause, should be able to handle whatever is happening now. Will post update shortly

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html


please try this

[TwitterNub]

OK giving it a shot now.

I downloaded new update you linked to me above. So far it seems to be working so I will give it a shot over the next day or 2 and let you know. Thanks Martin!