What Make.com has to say:

"Hi Jeroom,

Thanks for reaching out to us and for patiently waiting! My name is Ankita from the Make Customer Care team. I apologize sincerely for the considerable delay in our response. Presently, we are experiencing an influx of tickets, leading to significant backlogs that have adversely impacted our ability to promptly address inquiries.

Is the issue here is that you have more than 9 items in the dataset: [Dataset ID] and you are only getting 9 items?

This is not the issue of the maximum execution time of the scenario as for the free plan, the maximum execution time is 5 mins you can check the same in the below documentation:

https://www.make.com/en/help/general/pricing-parameters#features-list

The concern here is that the Apify API is only returning 9 items. The API call to retrieve all dataset items was successfully made from Make's end. However, we only received 9 items in the response from the Apify server. Unfortunately, Make has no control over this, as we display the data received from third parties without any alteration.

I would request you to test this API using any API testing tool, such as Postman. If you still receive only 9 items, despite there being 30 items, please reach out to the Apify team regarding this issue, as they will have more insights.

API documentation for your reference: https://docs.apify.com/api/v2#/reference"

Hello,

The dataset from your screenshot points to this run on your account. This run got only 10 results because it was prematurely aborted after running for 1m 13 sec. If you haven't abort it yourself, I would check if there isn't any Make config that could cause it.

Thank you for your reply. It was aborted manually (to save credits) after I saw that the "Run an actor" module stopped by itself after a minute. I'd gladly provide more context.

I still haven't figured out a fix.

Hello,

Have you spoken to the Make team? This problem doesn't look related to Apify in any way. I would love to help.

I haven't aside from the email above ensuring me it's on Apify's side. What do you suggest?

Actually, I spoke with our team more and it might be a limitation in our integration where Make newly allows 5 minutes but we only allow 2 minutes. I'm not sure how quickly can the team upgrade this, we will let you know.

There should also be a way for you to not be time limited, where the run finishing would cause a trigger in a next step independently of how long it runs.

Thanks for the update. I see what you mean, however all my runs finish after precisely 60 seconds and not 120. If you like we could call and I share my screen to show you everything that is happening, or I can try to screen record.

I'm not an expert on our Make integration so if you can screen record, send it here and I will share it with the team. That would help. Thank you.

Here is the link: https://streamable.com/e8rh5x (video expires in two days) I performed a couple tests, this is the last one. You can see my mouse hovering over the durations of the last tests, all ended at the same duration approx.

Thanks a lot, the team will debug that.

Ok, keep me posted! And let me know if can be of any more help

Hello,

We submitted a new version of the integration that should have 5-minute timeout. It should be released in couple of days once Make approves it.

Hi Lukas, thanks for the update, looking forward to trying it out.

Jeroom

Hello, update: it works well. However every now and then it still has that issue. Could it be because of an "unstable" internet connection on my end?