Google Shopping Insights avatar
Google Shopping Insights

Pricing

$30.00/month + usage

Go to Store
Google Shopping Insights

Google Shopping Insights

Developed by

epctex

epctex

Maintained by Community

Unlock valuable insights from Google Shopping with our Data Extractor. Get reviews, descriptions, prices, merchant details, and affiliation links. Export data in JSON, XML, CSV, Excel, and HTML formats with no limits!

3.6 (2)

Pricing

$30.00/month + usage

36

Total users

2K

Monthly users

32

Runs succeeded

>99%

Last modified

7 hours ago

ET

Actor stopped after first request

Closed

exquisite_tab opened this issue
2 years ago

The actor is stopping after the first request. It works only when I resurrect the whole run.

ET

exquisite_tab

2 years ago
TU

tugkan

2 years ago

Hey Šimon Kubita,

Unfortunately, we could not reproduce the issue. Can you please share your run ID with us? The problem might happened due to the Apify's own infrastructure.

Best

ET

exquisite_tab

2 years ago

Hello, thx for fixing it. This issue appears to me with every run.

examples: Q4XsFwPyiXukiB96T xL4cJacLsXsBfNKoh Epvqocp5y15ZhUItu

example with multiple resurrections: SGmiGdTM71QmwFISa

ET

exquisite_tab

2 years ago

One fresh run: EC5rpGZAANgWsNqUV

TU

tugkan

2 years ago

Hey Šimon Kubita,

Everything seems working properly on our side. Did you try to increase the Max Items (maxItems) attribute to retrieve more results? Or remove it completely?

Best

ET

exquisite_tab

2 years ago

I dont need more results. I need to Actor try every input (search query) and dont stop after first. Example EC5rpGZAANgWsNqUV has 4 inputs with 3 max items parameter but has only 3 results overall. In the header of the run is "Requests 1 of 5 handled".

ET

exquisite_tab

2 years ago

I need 4x3 results = 12 results.

ET

exquisite_tab

2 years ago

In the result data is only first search query.

ET

exquisite_tab

2 years ago

Can you reopen this issue, please? This is not fixed.

TU

tugkan

2 years ago

Hey Šimon Kubita,

Unfortunately, the maxItems attribute that we have in all of our public actors is not working by this logic. It is there to tweak the total number of items. If you want to have 3x4 = 12 results, my suggestion for you is to create 4 different tasks and proceed forward with it.

Please let me know if there is anything else we can do for you. Best

ET

exquisite_tab

2 years ago

What? How works input "search queries"? If I have 4 input queries (search query) with MaxItems 3 how many results are correct?

ET

exquisite_tab

2 years ago

This example

ET

exquisite_tab

2 years ago

I expect 12 results - 4 queries with 3 items per query. 12 results in the result set.

TU

tugkan

2 years ago

If maxItems have been provided, the total number of results will be equal to maxItems. For example; if you put 5 on the maxItems field, you'll only get 5 results in total.

On the other hand, search queries are there for running the public actor within multiple fields. As mentioned above, the best approach for this kind of case is to create 4 different tasks, put only 1 query, and add 3 as maxItems.

Best.

ET

exquisite_tab

2 years ago

I need to search 15k this queries. You are saying that i have to do 15k different tasks? Im convinced that this is not how this crawler was designed with input fields.

TU

tugkan

2 years ago

If you want to run the public actor programmatically and use it with 15K different queries, we can integrate a new field such as maxItemsPerQuery. Do you think this would resolve your problem?

ET

exquisite_tab

2 years ago

maxItemsPerQuery is what maxItems was originally designed for I mean. Yes, this would fix this problem.

maxItems how you described would be used only with one search query I mean. And with one query you dont need it, because you have maxItemsPerQuery :)

ET

exquisite_tab

2 years ago

I tried to delete maxItems input as you described and give 4 search queries. But this run crashed and now it's repeating request permanently. It won't stop. For now, has tried 33 requests and continues.

6UeLqgwbaR4o17v7d

ET

exquisite_tab

2 years ago

2023-02-13T18:19:45.479Z ACTOR: Pulling Docker image from repository. 2023-02-13T18:19:58.074Z ACTOR: Creating Docker container. 2023-02-13T18:20:02.533Z ACTOR: Starting Docker container. 2023-02-13T18:20:05.212Z INFO System info {"apifyVersion":"3.1.1","apifyClientVersion":"2.6.2","crawleeVersion":"3.2.2","osType":"Linux","nodeVersion":"v16.19.0"} 2023-02-13T18:20:05.223Z INFO PHASE -- STARTING ACTOR. 2023-02-13T18:20:05.476Z INFO PHASE -- SETTING UP CRAWLER. 2023-02-13T18:20:05.690Z INFO CRAWLER STARTED. 2023-02-13T18:20:07.596Z INFO PuppeteerCrawler: Starting the crawl 2023-02-13T18:20:20.081Z INFO CRAWLER: -- Found 60 items from http://www.google.cz/search?q=JOOP%20JUMP&tbm=shop&tbs=vw:l&start=0&gl=cz 2023-02-13T18:20:30.273Z INFO CRAWLER: -- Found 6 items from http://www.google.cz/search?q=LAMBRETTA%20PRIVATO&tbm=shop&tbs=vw:l&start=0&gl=cz 2023-02-13T18:20:38.230Z INFO CRAWLER: -- Found 20 items from http://www.google.cz/search?q=JOOP%20JUMP&tbm=shop&tbs=vw:l&start=60&gl=CZ 2023-02-13T18:20:39.506Z INFO CRAWLER: -- Found 60 items from http://www.google.cz/search?q=LALIQUE%20SOLEIL&tbm=shop&tbs=vw:l&start=0&gl=cz 2023-02-13T18:21:07.597Z INFO Statistics: PuppeteerCrawler request statistics: {"requestAvgFailedDurationMillis":null,"requestAvgFinishedDurationMillis":13842,"requestsFinishedPerMinute":4,"requestsFailedPerMinute":0,"requestTotalDurationMillis":55366,"requestsTotal":4,"crawlerRuntimeMillis":62016,"retryHistogram":[4]} 2023-02-13T18:21:07.... [trimmed]

ET

exquisite_tab

2 years ago

The searchKeyword is empty in the result set in most of them.

TU

tugkan

2 years ago

Hey Šimon Kubita,

We've integrated the maxItemsPerQuery field.

Best

ET

exquisite_tab

2 years ago

Hi, Nice! Thanks. But i tried it - pjhAfer3q1neKNMfc and have same trouble as my last comment. Pls can you check it?

ET

exquisite_tab

2 years ago

Inputs - maxPerQuery:3,queries:4,maxItems:null Results:600+

TU

tugkan

2 years ago

Hey Šimon Kubita,

The key must be maxItemsPerQuery. We updated the actor again for the broken key. If you are using the actor programmatically, you should use it in this way. About the issue you've been facing, the problem should be fixed just now. Can you please try it again?

Best

ET

exquisite_tab

2 years ago

Great! It works fine on test inputs. I will try it in production tomorrow. Many thanks!