🚨 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.
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.
