Apify & Crawlee

💻creators-and-apify

•

@Unknown user Please please change the language around pricing per record. Single result in the default dataset, literally shows $2.00/1000 instead of just 0.002, which from a selling perspective would make more sense.

At least change the lagnauge either to Pricing per 1000 results results on average $2.00 or change to $0.002 please

apify-platform

•

Hey, Error while publishing my Actor

Dead12/15/25, 5:31 PM

While publishing my actor, hitting with this error tried to wait some time but still it was the same. Please help me out with this.

🗣general-chat

•

I have a weird question, will the apify

thick-teal12/14/25, 3:12 PM

I have a weird question, will the apify team be able to view the actor code when valuating the challenge winners? I have a scraper that also can input apollo URL as input, but it doesnt use apollo just using url to extract users filters. Will it he eligible? Since in terms it says no apollo scrapers, or will they not be aboe to view the code and me naming it as a scraper without apollo works?

💻creators-and-apify

•

how to suppress warning message of an

fierDeToiMonGrand12/14/25, 4:09 PM

how to suppress warning message of an http crawler (crawlee), like I have set

log.setLevel(log.LEVELS.OFF);

log.setLevel(log.LEVELS.OFF);

and it still trows warning message saying

WARN  Request: We've encountered a POST Request with a payload. This is fine. Just letting you know that if your requests point to the same URL and differ only in method and payload, you should see the "useExtendedUniqueKey" option of Request constructor.

WARN  Request: We've encountered a POST Request with a payload. This is fine. Just letting you know that if your requests point to the same URL and differ only in method and payload, you should see the "useExtendedUniqueKey" option of Request constructor.

Like I know I could set the paremeter to remove the warning, but I explicitly don't want to use the parameter is there a way to supress the warning?

apify-platform

•

Hi team, I need urgent help with a billing issue.

Original message was deleted

💻creators-and-apify

•

Also most free users aren't gaming the

Lukas Krivka12/14/25, 11:15 AM

Also most free users aren't gaming the system. It is completely normal that most users are not paying, that's how every freemium model works. They might not need high workload or they are just trying things. Maybe they tried your Actor but liked other Actor more and only after that they subscribed.

If you can, don't rely on any 3rd party costs, then you can forget about the free users, Apify covers all Apify platform costs.

That being said, we know that many Actors have 3rd party limits so we want to approach this topic well. Currently, it is kinda wild west and most solutions have terrible UX, like not allowing API usage etc. In the future, there should be options for devs what to allow free users built into the system.

💻creators-and-apify

•

Hi @Saurav Jain Can you tell me

forward-apricot12/12/25, 9:07 AM

Hi @Saurav Jain Can you tell me whether we pay for the proxy usage, if we have an actor that use PPE

💻creators-and-apify

•

Hi! I'm receiving emails saying that one

igolaizola12/12/25, 7:51 AM

Hi! I'm receiving emails saying that one of my actors has a negative profit, but when I go to the console I see that it is positive.
Is there any existing bug on that part?

💻creators-and-apify

•

🚨 Bug Report: Charge API Idempotency

Aciku12/10/25, 5:57 PM

Bug Report: Charge API Idempotency
I was testing the endpoint https://api.apify.com/v2/actor-runs/:runId/charge.

The Setup:

I sent 378 requests to the Charge endpoint.
All requests used the exact same header: idempotency-key: asdfdfdf.

Expected Result:

The system should process 1 charge and return 201 for the rest (deduplicated).

Actual Result:

I was charged 4 times for the same key.

It seems like the idempotency check failed and allowed duplicates.

Logs: https://api.apify.com/v2/logs/4bvXcq1weMRaoTsN9

Could someone look into this? This is critical for preventing double-billing in actors.

apify-platform

•

Proxy: EU Based Static IP?

Moazzam Malek12/12/25, 2:14 PM

Hi Apify Team, By any chance you provide EU Based Static IP?

💫feature-request

•

Support for End-to-End HTTP/2 (gRPC) for

Aciku12/11/25, 4:38 PM

Support for End-to-End HTTP/2 (gRPC) for Actor Container URLs

The Problem:
I am building a high-performance Rust Actor using gRPC (Tonic) for internal data ingestion.
The Load Balancer appears to downgrade the connection to HTTP/1.1 when communicating with the Actor container.
This causes standard gRPC servers (like tonic in Rust or grpc-go) to crash immediately with Protocol Errors (HTTP 464) because they require an HTTP/2 transport layer.

The Request:
Please add an option in the actor.json or Input configuration to enable End-to-End HTTP/2 (or gRPC mode) for the Container Web Server.

apify-platform

•

Let us run PPE actors in development on Apify without providing pricing

Louis Deconinck12/11/25, 7:28 AM

I have my PPE actor ready and want to do a couple of test runs on Apify's platform to estimate the cost before publishing. At this moment I haven't yet defined pricing. I am always forced to remove the PPE pricing logic to do these runs. When I leave it in, I get this error:

/usr/src/app/node_modules/apify/charging.js:329const price = this.isAtHome ? this.pricingInfo[eventName].price : 1; // Use a nonzero price for local development so that the maximum budget can be reached
TypeError: Cannot read properties of undefined (reading 'price')
     at ChargingManager.calculateMaxEventChargeCountWithinLimit (/usr/src/app/node_modules/apify/charging.js:329:67)
     at file:///usr/src/app/dist/main.js:14:44
     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

/usr/src/app/node_modules/apify/charging.js:329const price = this.isAtHome ? this.pricingInfo[eventName].price : 1; // Use a nonzero price for local development so that the maximum budget can be reached
TypeError: Cannot read properties of undefined (reading 'price')
     at ChargingManager.calculateMaxEventChargeCountWithinLimit (/usr/src/app/node_modules/apify/charging.js:329:67)
     at file:///usr/src/app/dist/main.js:14:44
     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

This is cumbersome as it requires me to rebuild the actor a couple fo times. I only get this error when running on Apify, not locally. Am I doing something wrong?

apify-platform

•

🚨 Bug Report: Charge API Idempotency

Aciku12/10/25, 6:12 PM

I was testing the endpoint https://api.apify.com/v2/actor-runs/:runId/charge.

The Setup:

I sent 378 requests to the Charge endpoint.
- All requests used the exact same header: idempotency-key: asdfdfdf.
Expected Result:
The system should process 1 charge and return 201 for the rest (deduplicated).Actual Result:
- I was charged 4 times for the same key.
It seems like the idempotency check failed and allowed duplicates.

Logs: https://api.apify.com/v2/logs/4bvXcq1weMRaoTsN9

Could someone look into this? This is critical for preventing double-billing in actors.

Screenshot_2025-12-10_at_12.56.08_PM.png

Screenshot_2025-12-10_at_12.56.46_PM.png

💻creators-and-apify

•

is there a way to create your own

fierDeToiMonGrand12/10/25, 1:07 PM

is there a way to create your own proxies?

apify-platform

•

About: enumSuggestedValues setting

!!!Joefree!!! 👑12/9/25, 1:29 PM

Thank you for new addition to input_schema "enumSuggestedValues"

I am using enumSuggestedValues on an array input, I notice 2 difference :

bulk edit functionality is gone.
unable to input duplicate value.

I just want to clarify whether this is a bug or intended behavior.
Thank You.

crawlee-python

•

Can your LinkedIn Company Employee Scrapers access 'People' tab

Bo12/9/25, 4:41 AM

without a LinkedIn session cookie (li_at)? I’m on the Free plan and the actor has no field for a cookie. Before I upgrade, I need a yes/no: does this actor support authenticated scraping at all, and if so, where is the cookie input located? If it cannot scrape employee lists without authentication, then upgrading won’t fix anything, because it will still be blocked at the UI level. The results I'm getting are mixed at best and I'm told it's because it is not an authenticated search.

apify-platform

•

SSE Dead Client Detection Issue Behind Apify Standby Proxy

Muhammet12/7/25, 9:40 AM

In my SSE endpoint running under Apify Standby mode, the server is unable to reliably detect when clients disconnect. Even when the client closes the browser or loses network connection, the Apify proxy keeps the connection to the Actor open, so the server never receives a proper “disconnect” signal. As a result, the server continues to treat the connection as active and keeps streaming data to a client that no longer exists. Over time, this leads to accumulated dead connections, unnecessary resource usage, and inaccurate connection metrics.

The core issue appears to be that Apify’s proxy does not propagate the actual client disconnect to the Actor. Therefore:

```
close
```
```
close
```
,
```
error
```
```
error
```
, and timeout events are never triggered on the server side,
the server continues writing data with no feedback that the real client is gone,
stale SSE connections remain in memory and cannot be cleaned up correctly.

I currently rely on several heuristic workarounds, such as:

marking a connection as dead if no successful write occurs within a certain time window,
monitoring pending writes to detect possible dead streams,
running periodic checks to validate connection state.

These strategies help mitigate the issue but are not fully reliable, since they rely on indirect signals rather than a definitive disconnect notification from the network layer.

For this reason, I need clarification on the following points:

Does Apify Standby mode enforce any specific timeout, keep-alive, or proxy behavior for SSE connections?
Is there any officially recommended method to detect dead SSE clients when running behind the Apify proxy?
Can additional HTTP headers influence how the proxy handles disconnects or keep-alives?

apify-platform

•

BUG: Build not Sorted correctly

!!!Joefree!!! 👑12/7/25, 3:51 AM

Build versions not sorted correctly, for example this case. 0.10 version should be at the bottom

🗣general-chat

•

Im at SF hackathon event is there a 2nd

colossal-harlequin12/6/25, 7:15 PM

Im at SF hackathon event is there a 2nd wifi that has capacity?

WARN Request: We've encountered a POST Request with a payload. This is fine. Just letting you know that if your requests point to the same URL and differ only in method and payload, you should see the "useExtendedUniqueKey" option of Request constructor.

/usr/src/app/node_modules/apify/charging.js:329const price = this.isAtHome ? this.pricingInfo[eventName].price : 1; // Use a nonzero price for local development so that the maximum budget can be reached TypeError: Cannot read properties of undefined (reading 'price') at ChargingManager.calculateMaxEventChargeCountWithinLimit (/usr/src/app/node_modules/apify/charging.js:329:67) at file:///usr/src/app/dist/main.js:14:44 at process.processTicksAndRejections (node:internal/process/task_queues:105:5)