Search flooding since update

[LuckyLuke]

Hi martin,

since update 3.447 when "search & reply" action, the bot keeps flooding search results on all actions. Bot is set to Max 1 hour since last tweet "@username > user ID > User tweet" and check tweets for page 1 and finishes action, now since the update it keeps checking page on page non stop and won't stop the process, flooding it. There are NO LOGS because it's no error but I have to manually cancel the action otherwise it keeps going forever and I'm worried it will count towards limit rate.

Normally bot stops after Search Page 1 (see below I put on BOLD) and closes process, now bot keeps going Search Page 2, 3, 4 etc.. and never stops bringing up from 1000's hour ago but ignore because Max is set to 1 hour. I rever back to versio 3.446 and it works again, even new versions 3.449/3.450 have same problem with flooding.

See below for example

Code: Select all

Starting: 04/07/2023 15:54 PM
 Search: Custom
Num: 1
Unique: True
Custom Search: A User Id or Url-LatestTweetOf

*** Performing Search ***
performSearchOfTerm
Searching:@elonmusk : max: 1
First run shuffle accounts
Selected account: BOT
Check term for tokens: @elonmusk
custom search builder
Selected account: BOT
ABallard60486 Loaded previous db logs: Id: 13ea000001814a8e90e_ReplyTweet Data: 18 Ids: 18 Processed: 9 24: 0 Today: 0 GlobalCount: 0
Max Results Wanted: 1
Search: @elonmuskmax: 1
Setup custom search controller
Custom search run: search: @elonmusk
A User Id or Url-LatestTweetOf
Perform custom search: 'A User Id or Url' #chain/total: 1/2 using: BOT
Cannot request unlimited items per chained search: setting: 100
Start search: A User Id or Url with: @elonmusk(100) using: BOT
Results of search: 1/100 A User Id or Url with: @elonmusk
Handle results: 1 nextstep: 2/2
Got results from chain: 1 feed into next chained custom search item
Handle Result:https://twitter.com/elonmusk  step: 1/2 Result: 1/1
Perform chained search: [1] https://twitter.com/elonmusk
Perform custom search: 'LatestTweetOf' #chain/total: 2/2 using: BOT
User specific num per stage to return: 1
Start search: LatestTweetOf with: https://twitter.com/elonmusk(1) using: BOT
Get latest tweet: https://twitter.com/elonmusk
Search: https://twitter.com/elonmusk with: BOT: max: 1 return: RETURN_URLS
userfeed: UID: 44196397 https://twitter.com/elonmusk
Get cursor
[b]Search pages: 1[/b]
Value: 61 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675315530725556224 https://twitter.com/elonmusk/status/1675315530725556224
* IGNORE: Filtered: 1675315530725556224
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 61 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675315349573578752 https://twitter.com/elonmusk/status/1675315349573578752
* IGNORE: Filtered: 1675315349573578752
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 61 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675309846701174786 https://twitter.com/elonmusk/status/1675309846701174786
* IGNORE: Filtered: 1675309846701174786
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 65 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675258297358643200 https://twitter.com/elonmusk/status/1675258297358643200
* IGNORE: Filtered: 1675258297358643200
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 66 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675231028183433218 https://twitter.com/elonmusk/status/1675231028183433218
* IGNORE: Filtered: 1675231028183433218
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 68 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675210005073600512 https://twitter.com/elonmusk/status/1675210005073600512
* IGNORE: Filtered: 1675210005073600512
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 70 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675184592700014595 https://twitter.com/elonmusk/status/1675184592700014595
* IGNORE: Filtered: 1675184592700014595
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 70 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675184083805118464 https://twitter.com/elonmusk/status/1675184083805118464
* IGNORE: Filtered: 1675184083805118464
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 70 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675183424133292032 https://twitter.com/elonmusk/status/1675183424133292032
* IGNORE: Filtered: 1675183424133292032
Filter check: https://twitter.com/Shopping_Tools
Filter user: https://twitter.com/Shopping_Tools  : Shopping_Tools
Filter allowed: https://twitter.com/Shopping_Tools
Checking Filter: MaxHoursSinceTweet
Value: 82 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674990342037204994 https://twitter.com/Shopping_Tools/status/1674990342037204994
* IGNORE: Filtered: 1674990342037204994
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 84 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674963647225896961 https://twitter.com/elonmusk/status/1674963647225896961
* IGNORE: Filtered: 1674963647225896961
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 89 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674894268912087040 https://twitter.com/elonmusk/status/1674894268912087040
* IGNORE: Filtered: 1674894268912087040
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 103 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674678484780580864 https://twitter.com/elonmusk/status/1674678484780580864
* IGNORE: Filtered: 1674678484780580864
Filter check: https://twitter.com/StensonTamaddon
Filter user: https://twitter.com/StensonTamaddon  : StensonTamaddon
Filter allowed: https://twitter.com/StensonTamaddon
Checking Filter: MaxHoursSinceTweet
Value: 4194 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1612920969441562663 https://twitter.com/StensonTamaddon/status/1612920969441562663
* IGNORE: Filtered: 1612920969441562663
Filter check: https://twitter.com/SurveyCompareUS
Filter user: https://twitter.com/SurveyCompareUS  : SurveyCompareUS
Filter allowed: https://twitter.com/SurveyCompareUS
Checking Filter: MaxHoursSinceTweet
Value: 4344 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1610652085283954688 https://twitter.com/SurveyCompareUS/status/1610652085283954688
* IGNORE: Filtered: 1610652085283954688
Results: 0
Get cursor
[b]Search pages: 2[/b]
Paused for 6secs
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 106 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674635153061330946 https://twitter.com/elonmusk/status/1674635153061330946
* IGNORE: Filtered: 1674635153061330946
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 110 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674573540065148928 https://twitter.com/elonmusk/status/1674573540065148928
* IGNORE: Filtered: 1674573540065148928
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 118 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674454264993951744 https://twitter.com/elonmusk/status/1674454264993951744
* IGNORE: Filtered: 1674454264993951744
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 133 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674226170488057856 https://twitter.com/elonmusk/status/1674226170488057856
* IGNORE: Filtered: 1674226170488057856
Filter check: https://twitter.com/27mirror
Filter user: https://twitter.com/27mirror  : 27mirror
Filter allowed: https://twitter.com/27mirror
Checking Filter: MaxHoursSinceTweet
Value: 134 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674214860731604997 https://twitter.com/27mirror/status/1674214860731604997
* IGNORE: Filtered: 1674214860731604997
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 141 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1674101384390782976 https://twitter.com/elonmusk/status/1674101384390782976
* IGNORE: Filtered: 1674101384390782976
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 150 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673976802103148544 https://twitter.com/elonmusk/status/1673976802103148544
* IGNORE: Filtered: 1673976802103148544
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 159 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673832186796179456 https://twitter.com/elonmusk/status/1673832186796179456
* IGNORE: Filtered: 1673832186796179456
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 159 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673831774038949888 https://twitter.com/elonmusk/status/1673831774038949888
* IGNORE: Filtered: 1673831774038949888
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 166 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673725459689885703 https://twitter.com/elonmusk/status/1673725459689885703
* IGNORE: Filtered: 1673725459689885703
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 177 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673564912948326400 https://twitter.com/elonmusk/status/1673564912948326400
* IGNORE: Filtered: 1673564912948326400
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 186 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673428147650326528 https://twitter.com/elonmusk/status/1673428147650326528
* IGNORE: Filtered: 1673428147650326528
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 207 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1673110480276303872 https://twitter.com/elonmusk/status/1673110480276303872
* IGNORE: Filtered: 1673110480276303872
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 228 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1672795483712913410 https://twitter.com/elonmusk/status/1672795483712913410
* IGNORE: Filtered: 1672795483712913410
Filter check: https://twitter.com/KlinioApp
Filter user: https://twitter.com/KlinioApp  : KlinioApp
Filter allowed: https://twitter.com/KlinioApp
Checking Filter: MaxHoursSinceTweet
Value: 4422 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1609475443568136193 https://twitter.com/KlinioApp/status/1609475443568136193
* IGNORE: Filtered: 1609475443568136193
Results: 0

ON VERSION 3.446 THIS IS HOW IT WORKS NORMAL, MAX HOUR 40 NO FLOODING OF SEARCH RESULTS.

Setup custom search controller
Custom search run: search: @elonmusk
https://twitter.com/i/api/1.1/users/loo ... e=elonmusk
Total results: 1
* SUCCESS: UserDetails: https://twitter.com/elonmusk with: BOTProxy:
userfeed: UID: 44196397 https://twitter.com/elonmusk
Search pages: 1
Paused for 6secs
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 40 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1675628021909258240 https://twitter.com/elonmusk/status/1675628021909258240
Results of search: 0/1 LatestTweetOf with: https://twitter.com/elonmusk
Handle results: 0 nextstep: 3/2
End of chain: Store results: 0
Finished search: results: 0
Found after search: 0

etc.. and it keeps going forever, process never ends.

[martin@rootjazz]

ok seems a bug in the update for LATEST TWEET

which should return the latest tweet and that's it.

Looks like it is working like USER TWEETS (1)

which, due to your filter failing the item, it tries older items until it does match the filter.


Let me fix that and get it in to the next update (expected in 10-20 minutes)



Regards,
Martin

[martin@rootjazz]

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



try this please



Regards,
Martin

[LuckyLuke]

thanks martin, I normally use latest tweet or USER TWEET but before update 3.447 even with USER TWEET it just checked first page and then stopped process. The update 3.451 fixed the "latest tweet" option but the user tweet still keeps searching until forever, even with 1 hour max filter on.

Is there a way to make the process stop after page 1 (with USER TWEET, RECENT TWEET, USER REPLIES etc... because all those options make the process endless and it keeps searching forever) as it always used to be in version 3.446 for example?

Below is the process now user replies for example and then it continues until forever, so user replies, recent tweet of, user tweets all processes will loop "forever" and never finish going back 1000's hours too in the search. Before they always used to stop after Search Page 1

Code: Select all

Selected account: BOT
BOT Loaded previous db logs: Id: 13ea1e32-3c6d-4e26-b1f8-331814a8e90e_ReplyTweet Data: 18 Ids: 18 Processed: 9 24: 0 Today: 0 GlobalCount: 0
Max Results Wanted: 1
Search: @elonmuskmax: 1
Setup custom search controller
Custom search run: search: @elonmusk
A User Id or Url-User Replies
Perform custom search: 'A User Id or Url' #chain/total: 1/2 using: BOT
Cannot request unlimited items per chained search: setting: 100
Start search: A User Id or Url with: @elonmusk(100) using: BOT
Results of search: 1/100 A User Id or Url with: @elonmusk
Handle results: 1 nextstep: 2/2
Got results from chain: 1 feed into next chained custom search item
Handle Result:https://twitter.com/elonmusk  step: 1/2 Result: 1/1
Perform chained search: [1] https://twitter.com/elonmusk
Perform custom search: 'User Replies' #chain/total: 2/2 using: BOT
User specific num per stage to return: 1
Start search: User Replies with: https://twitter.com/elonmusk(1) using: BOT
absearch: alreadyprocessed: 18
Search: https://twitter.com/elonmusk with: BOT: max: 1 return: RETURN_URLS
Notice: didn't handle content type: profile-conversation-1676309734359040000
Notice: didn't handle entry type: TimelineTimelineModule
found: https://twitter.com/elonmusk/status/1676254702772670465
found: https://twitter.com/NordaceOfficial/status/1674058654926905354
Notice: didn't handle content type: profile-conversation-1676309734359040003
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: who-to-follow-1676309734359040004
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040005
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040006
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040007
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040008
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040009
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040010
Notice: didn't handle entry type: TimelineTimelineModule
found: https://twitter.com/USD_LEPSL/status/1665790785248452609
Notice: didn't handle content type: profile-conversation-1676309734359040012
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040013
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040014
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040015
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040016
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040017
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040018
Notice: didn't handle entry type: TimelineTimelineModule
Notice: didn't handle content type: profile-conversation-1676309734359040019
Notice: didn't handle entry type: TimelineTimelineModule
found: https://twitter.com/Geeky_Base/status/1674351513693462528
Notice: didn't handle content type: profile-conversation-1676309734359040021
Notice: didn't handle entry type: TimelineTimelineModule
Cursor: DAABCgABF0Ny0mn__-gKAAIXQgou3VewDggAAwAAAAIAAA
Search pages: 1

[martin@rootjazz]

Notice: didn't handle content type: profile-conversation-1676309734359040019
Notice: didn't handle entry type: TimelineTimelineModule

ok these are search results program cannot handle for that search. I think it's a tweet that has replies, I will need to check.


As for the other issue, yes as I need to add back in the "stop searching" checks, when the program knows there will be possibility of new results (tweets are after the max filter time_since).


There will be quite a lot of these types of functions to add back in as search has been completely rewritten to the new style

[martin@rootjazz]

Is there a way to make the process stop after page 1 (with USER TWEET, RECENT TWEET, USER REPLIES etc... because all those options make the process endless and it keeps searching forever) as it always used to be in version 3.446 for example?

actually, are you sure previous version for:

USER TWEETS
RECENT (is the same as USER TWEETS)
REPLIES

used to stop? I don't think it did, if you wanted (x) results the search will continue looking until it finds (x). If your filter ignores all results it will search for ever (eventually I think a protection kicks in stop after 100 pages with no results or something. But it wouldn't stop after one page previous (apart from a filter that could no longer find results as mentioned in post above)


What I can do, is add a token option for all searches,

so if your search is
@elonmust

you can specify a onepage only search with

@elonmusk 1page

and it will stop after the first page of results have been checked whether it found your results or not.


The program with adding protectings such as "no results after 10 pages then stop" someone will want to, so I always annoy someone somewhere somehow

I think 1page in the input would work, ideas?

[martin@rootjazz]

next update allows search control tokens

Code: Select all

1page
maxpages=N

where N can be the maximum number of search pages


Tutorial
viewtopic.php?f=32&t=11973&p=76140#p76140

[LuckyLuke]

Martin,

I downgraded to 3.446 and ran USER TWEET search, this is what it looked like then with all search options (latest tweet, user tweet, recent tweet of) it did not even list all the amount of tweets to ignore but checked and saw 4 hours since max tweet and stopped process. So since the "user reply" function added in 3.447 it seems to skip it and keeps searching page after page.

EDIT: just saw your update above, probably a good solution, I just want to check, you think if bot searches 1 whole page, do all tweets on the page count towards rate limit? On 3.446 it seems to only check latest tweet even with USER TWEET option which was always perfect for me but I understand other users have different uses.

Code: Select all

Search: @elonmuskmax: 1
Setup custom search controller
Custom search run: search: @elonmusk
[b]A User Id or Url-User tweets[/b]
Perform custom search: 'A User Id or Url' #chain/total: 1/2 using: BOT
Cannot request unlimited items per chained search: setting: 100
Start search: A User Id or Url with: @elonmusk(100) using: BOT
Results of search: 1/100 A User Id or Url with: @elonmusk
Handle results: 1 nextstep: 2/2
Got results from chain: 1 feed into next chained custom search item
Handle Result:https://twitter.com/elonmusk  step: 1/2 Result: 1/1
Perform chained search: [1] https://twitter.com/elonmusk
Perform custom search: 'User tweets' #chain/total: 2/2 using: BOT
User specific num per stage to return: 1
Start search: User tweets with: https://twitter.com/elonmusk(1) using: BOT
absearch: alreadyprocessed: 18
Search: https://twitter.com/elonmusk with: BOT: max: 1 return: RETURN_URLS
Get User: https://twitter.com/elonmusk with: BOT
UserDetails: https://twitter.com/elonmusk with: BOT  Proxy:  
Scrape from users: 1
Scrape details from: 1 inputs
Getting user details for :1 ids
200
https://twitter.com/i/api/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=elonmusk
Total results: 1
* SUCCESS: UserDetails: https://twitter.com/elonmusk with: BOT  Proxy:
userfeed: UID: 44196397 https://twitter.com/elonmusk
Search pages: 1
Paused for 8secs
Filter check: https://twitter.com/elonmusk
Filter user: https://twitter.com/elonmusk  : elonmusk
Filter allowed: https://twitter.com/elonmusk
Checking Filter: MaxHoursSinceTweet
Value: 4 is <0 or > 1
* IGNORE: MaxHoursSinceTweet: 1676254702772670465 https://twitter.com/elonmusk/status/1676254702772670465
Results of search: 0/1 User tweets with: https://twitter.com/elonmusk
Handle results: 0 nextstep: 3/2
End of chain: Store results: 0
Finished search: results: 0
Found after search: 0
Remove already processed items from list: Original: 0
Selected account: BOT
account: BOT load previously processed items
Removing already process items of: BOT
BOT Loaded previous db logs: Id: 13ea1e32-3c6d-4e26-b1f8-331814a8e90e_ReplyTweet Data: 18 Ids: 18 Processed: 9 24: 0 Today: 0 GlobalCount: 0
Checking results: 0 against already processed list: 18 of: BOT
Finish removing already processed: results :0 removed already processed: 0
Selected account: BOT
Checking to remove any of (0) already previous items from merged logs: 18
Nothing removed: 0
WARNING no items to process: ReplyTweet

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

[martin@rootjazz]

Martin,

I downgraded to 3.446 and ran USER TWEET search, this is what it looked like then with all search options (latest tweet, user tweet, recent tweet of) it did not even list all the amount of tweets to ignore but checked and saw 4 hours since max tweet and stopped process. So since the "user reply" function added in 3.447 it seems to skip it and keeps searching page after page.

Yes as I said, the filters need to be updated so can trigger a search to stop when there is no chance of any more results.
example: max tweet date has been passesd.
Only going to get older and older tweets, so it needs to stop.

I need to add this code.

[martin@rootjazz]

the new update has the code in, but it's not working. So don't use the tokens yet