Repeated failed json responses after password reset

[lsberic]

I am getting a lot of errors in my log that look like this:

Couldn't pass JSON response from search
* FAILED: 23************* : no results
FAILED GET: (5*****) 500

and like this


https://twitter.com/i/api/1.1/users/loo ... =<USERNAME>
No users found for: https://twitter.com/<USERNAME>
* FAILED: UserDetails: https://twitter.com/<USERNAME> with: <USERNAME>
Checking daily limits: <USERNAME>
Global Daily limit: 0
Posting: 82******* to <USERNAME>
Preprocess image: Thumbs.db
PostImage: with: <USERNAME> No Proxy
Global Daily limit: 0

(where <username> is my username and asterisk have been added to block any sensitive information)

This occured after I was forced to reset my password due to "unusual" activity.

Is this something to worry about and fix?

[martin@rootjazz]

Logs please:

HELP > LOGS > SUBMIT

then send your logs ID - the numbers are sufficient (displayed after successful uploading of logs)

[lsberic]

Logs please:

HELP > LOGS > SUBMIT

then send your logs ID - the numbers are sufficient (displayed after successful uploading of logs)

ID: 43088

[martin@rootjazz]

Lots and lots of server errors reported. Unsure why.




Please perform the following:

Open the program.

Delete or pause all existing actions. If actions are already running due to autorun on startup, disable autorun at startup and restart the app. Then pause all (or delete) ALL actions must be waiting / paused,

Delete existing logs
HELP > LOGS > DELETE
or
HELP > LOGS > VIEW and delete all files in folder that opens


Perform the action:
***


Goto the ACCOUNTS tab
Check the account
Right click the account and select DELETE COOKIES
Uncheck option to USE EXISTING COOKIES (if open exists)
Check Force (if option exists)
click the link VERIFY:LOGIN

This will create an action and send it to the PROCESSING TAB
Goto the processing tab and click RUN. The action will run.
You can double click the action to view the logs and submit logs.


If that all goes through fine, then try a simple action you were having trouble with. If the issue persists submit logs
***

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)




Regards,
Martin