Hi Rob, thanks for the report. I believe that is not the case, that's only the maximum you set but not what you should be charged. Logs say you were only charged for 701 items in queue before the actor had a chance to get the results and that should be 701 * 0.005 = ~ USD 3.5 - if the actor had a chance to return results then it would be USD 0.01 per item * 701 items = ~ 7 USD

Let me know if that checks out

Frankly, I don't quite understand what's going on from the run you shared and the logs and info displayed there don't help much. The actor should charge USD 0.005 per item in the queue and then the same for item in result dataset. The overcharge message does not make sense to me. Even 864 * 0.005 is not equal to $57 remotely.

The other number you mentioned 7.67 would equal either 767 results in dataset or double the amount of items in queue for further processing.

Do let me know if something still seems off.

It's very off - I'm not even using it and I was just charged again >$24! How do stop these charges? https://console.apify.com/actors/runs/L74LkmASkduwF24Ks#output

See attached screenshot - those are billed charges - I keep increasing my usage limit and it keeps charging until my limit!

Okay, right now, I'm not sure what is going on so I would suggest that you disable the actor or whatever API calls are triggering it to prevent further escalation and have time to look into it.

Preferably, disable whatever application is calling the actor via API on your behalf or disable any tokens directly linked with it before it can be investigated further.

The charge occurred at 14:51 (2:51 PM) during our active agentic coding development session when I was:

Testing the Chrome Store collector implementation Running backend tests Testing API endpoints The 563 requests with 0 results pattern is exactly what we were trying to avoid with the cost controls.

Accidental API call during development/testing - Returned 0 results despite 563 requests Implementing cost controls to prevent this.

A refund would be greatly appreciated - didn't expect to spend >$100 today on this

I have reached out to support to check what's going on as there is nothing obvious to me at this point.

Okay, that is definitely wrong and warrants a refund because as mentioned the price per item is 0.01 split in half (0.005 during queue phase and the same during output)

Something is apparently off - let's see if support can help.

PS: there was also an announcement about the need for a complete rewrite of the actor plus change in pricing about two weeks ago, maybe you have missed that. But anyway, the pricing you mentioned is very wrong.

It should be dollar units tops for this amount of items put in queue, not tens or hundreds for sure. You can set the required amount of results on input separately.

Yeah, something is definitely off and I want to use this Actor, but now have to be very careful because I can't afford these crazy high charges - a refund would be great

Hi again - I think I know what the issue was. There is a native queue deduplication feature in Apify Request queue but it does not seem to have worked as expected in this case. Therefore instead of for each new set of items loaded it was charging for total items loaded every time a new batch was added - I have requested a refund on your behalf and still looking into it but the issue should be fixed now. Here is an example: https://console.apify.com/view/runs/ah4ebqrFil1e50K6k

Apologies about the inconvenience. I believe the refund process will be smooth.

Hello, just an update that the refund is being processed.

I see they credited my account $58, but what about the other charges? There was another $40+ in erroneous charges in addition to that one charge of $58

These are the 4 charges I incurred: $57.75 + $7.67 + $7.67 + $24.67 = $97.76

Hello, sorry about the delay, will check with them and get back to you. Thanks for your patience.