Issue With Failing Actions

[martin@rootjazz]

This time one action ran.

But what is the problem?

The program appears to be running:

11:25:48: Results of search: All track interactions

and you submitted logs at

11:25:50: submit logs

Did the action keep running?
Or had the action failed then? I don't think so as failed actions log out and the logs look like they were stopped midway through (submitting logs)

[martin@rootjazz]

I tested what I think you are doing.

open app
goto like tab
check my account
enter the track url you used in your logs
click custom search
TRACK INTERACTIONS
LATEST TRACK OF
run action

runs through, scrapes the on liker of the track, gets their most recent track and likes it.

[wowthatscool]

I tested what I think you are doing.

open app
goto like tab
check my account
enter the track url you used in your logs
click custom search
TRACK INTERACTIONS
LATEST TRACK OF
run action

runs through, scrapes the on liker of the track, gets their most recent track and likes it.

yes it does it. But it takes days when it used to take hours. im gonna try to do a longer one than 1 like and see what happens

[wowthatscool]

I tested what I think you are doing.

open app
goto like tab
check my account
enter the track url you used in your logs
click custom search
TRACK INTERACTIONS
LATEST TRACK OF
run action

runs through, scrapes the on liker of the track, gets their most recent track and likes it.

yes it does it. But it takes days when it used to take hours. im gonna try to do a longer one than 1 like and see what happens

ok i tried a larger one and it been stuck on the same log for 2 hours. 98255. Its not check tracks or anything. Its just stuck on "Start search: Latest track of with: https://soundcloud.com/anthony-sanchez-471512724(10) using: smoke crack
absearch: alreadyprocessed: 3563"

[wowthatscool]

I tested what I think you are doing.

open app
goto like tab
check my account
enter the track url you used in your logs
click custom search
TRACK INTERACTIONS
LATEST TRACK OF
run action

runs through, scrapes the on liker of the track, gets their most recent track and likes it.

yes it does it. But it takes days when it used to take hours. im gonna try to do a longer one than 1 like and see what happens

ok i tried a larger one and it been stuck on the same log for 2 hours. 98255. Its not check tracks or anything. Its just stuck on "Start search: Latest track of with: https://soundcloud.com/anthony-sanchez-471512724(10) using: smoke crack
absearch: alreadyprocessed: 3563"

Update : It is stil stuck on the same line. It hasnt done anything

[wowthatscool]

yes it does it. But it takes days when it used to take hours. im gonna try to do a longer one than 1 like and see what happens

ok i tried a larger one and it been stuck on the same log for 2 hours. 98255. Its not check tracks or anything. Its just stuck on "Start search: Latest track of with: https://soundcloud.com/anthony-sanchez-471512724(10) using: smoke crack
absearch: alreadyprocessed: 3563"

Update : It is stil stuck on the same line. It hasnt done anything

Update : I got up this morning and it still hasnt done anything.

[martin@rootjazz]

I tested what I think you are doing.

open app
goto like tab
check my account
enter the track url you used in your logs
click custom search
TRACK INTERACTIONS
LATEST TRACK OF
run action

runs through, scrapes the on liker of the track, gets their most recent track and likes it.

yes it does it.

so it works fine for you doing the above?

But it takes days when it used to take hours.

Let me know an example of what doesn't work and I can check. But if your input has 100 tracks with 100,000 likes each, that is a lot of scraping thus will take longer

[martin@rootjazz]

I tested what I think you are doing.

open app
goto like tab
check my account
enter the track url you used in your logs
click custom search
TRACK INTERACTIONS
LATEST TRACK OF
run action

runs through, scrapes the on liker of the track, gets their most recent track and likes it.

yes it does it. But it takes days when it used to take hours. im gonna try to do a longer one than 1 like and see what happens

ok i tried a larger one and it been stuck on the same log for 2 hours. 98255. Its not check tracks or anything. Its just stuck on "Start search: Latest track of with: https://soundcloud.com/anthony-sanchez-471512724(10) using: smoke crack
absearch: alreadyprocessed: 3563"

Please detail what you are doing, as your test is not the same as above but with a different input. You've set a filter, so right away, that means each potential results requires additional requests to get and test the info.

Whereas without the filter, you can avoid those additional requests.

But again, your logs indicate the action is running when you submit logs, there does not appear to be any freezing.

But, you didn't clear the logs before the test, so is hard to know exactly what you are referring to.


Just to reiterate, before running a test. ALWAYS CLEAR LOGS
HELP > LOGS > VIEW > delete all.

That way, the only logs present are related to your test. It is possible there is one log line that explains what is happening, but when hidden between 10s or 100s of actions, it is like a needle in a haystack.

Again, if you can specify EXACTLY what you are doing (as I posted above).

open app
goto tab
click this
select that
...
etc

I can replicate EXACTLY what you are doing, and if I do exactly the same, I will get the same results.




Regards,
Martin

[wowthatscool]

yes it does it. But it takes days when it used to take hours. im gonna try to do a longer one than 1 like and see what happens

ok i tried a larger one and it been stuck on the same log for 2 hours. 98255. Its not check tracks or anything. Its just stuck on "Start search: Latest track of with: https://soundcloud.com/anthony-sanchez-471512724(10) using: smoke crack
absearch: alreadyprocessed: 3563"

Please detail what you are doing, as your test is not the same as above but with a different input. You've set a filter, so right away, that means each potential results requires additional requests to get and test the info.

Whereas without the filter, you can avoid those additional requests.

But again, your logs indicate the action is running when you submit logs, there does not appear to be any freezing.

But, you didn't clear the logs before the test, so is hard to know exactly what you are referring to.


Just to reiterate, before running a test. ALWAYS CLEAR LOGS
HELP > LOGS > VIEW > delete all.

That way, the only logs present are related to your test. It is possible there is one log line that explains what is happening, but when hidden between 10s or 100s of actions, it is like a needle in a haystack.

Again, if you can specify EXACTLY what you are doing (as I posted above).

open app
goto tab
click this
select that
...
etc

I can replicate EXACTLY what you are doing, and if I do exactly the same, I will get the same results.




Regards,
Martin

This is what im doing
DELETE MY OLD PROCESS
GO UP TO HELP AND VIEW LOGS FOLDER AND DELETE ALL FILES
GO TO FAVORITES TAB
CHECK ONE ACCOUNT ON THE LEFT SIDE
ADD LINK TO CUSTOM SEARCH BOX
BUILD CUSTOM SEARCH TRACK INTERACTIONS, LATEST TRACK
FILTER, EVERY SETTING AT 0 EXCEPT TRACK BY ARTIST ONCE EVERY X DAYS IS SET TO 360
MAX FAV SETTING SET TO 2000
PAUSE SET AT 3-10
ALL REPEATS ON 0
LIKE TRACK ONCE AND PLAY TRACK ARE CHECKED
CLICK SEARCH
GO TO PROCESSESS AND RIGHT CLICK AND PRESS RUN NOW
GO UP TO HELP AND SUBMIT LOGS

my number is 61216. Thank you for trying to help i know its frustrating

[martin@rootjazz]

This is what im doing
DELETE MY OLD PROCESS
GO UP TO HELP AND VIEW LOGS FOLDER AND DELETE ALL FILES
GO TO FAVORITES TAB
CHECK ONE ACCOUNT ON THE LEFT SIDE
ADD LINK TO CUSTOM SEARCH BOX
BUILD CUSTOM SEARCH TRACK INTERACTIONS, LATEST TRACK
FILTER, EVERY SETTING AT 0 EXCEPT TRACK BY ARTIST ONCE EVERY X DAYS IS SET TO 360
MAX FAV SETTING SET TO 2000
PAUSE SET AT 3-10
ALL REPEATS ON 0
LIKE TRACK ONCE AND PLAY TRACK ARE CHECKED
CLICK SEARCH
GO TO PROCESSESS AND RIGHT CLICK AND PRESS RUN NOW
GO UP TO HELP AND SUBMIT LOGS

my number is 61216. Thank you for trying to help i know its frustrating

ok, seems straight forward.
Having the filter, will increase time somewhat - the additional requests and the filtered out results mean have to check more results.

But it shouldn't freeze or anything. Let me check the logs now and run the exact test