[Pijukatel]

After a reboot, migration or restart, the platform seeds the new container with the charged event counts recorded when the run started, so the charging manager began from a fresh max_total_charge_usd budget. The SDK now reads the run before its first charge and continues from what was already charged.

• On a platform pay-per-event run with at least one event the SDK can charge, the charge lock reads the run the first time it is taken, which is before the first charge() or budgeted push_data() and updates the charge info from API.
• Reading late and lazily as opposed to eager reading on init gives the platform time to report correct values that can lag due to eventual consistency. Also there is no pre-emptive API call if no charging is used.
• Runs without SDK-chargeable events, non-PPE runs and local runs make no extra request. A failed read is logged and the env var counts are kept.
• The synchronous read methods report the start-of-run counts until that first charge or push. Making them async, so they trigger the load too would be a breaking change. (Can be potentially done for the next major release.)

Closes: #1209

[codecov]

Codecov Report

❌ Patch coverage is 94.87179% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.43%. Comparing base (4556821) to head (47c2926).
⚠️ Report is 5 commits behind head on master.

Files with missing lines	Patch %	Lines
src/apify/_charging.py	94.87%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1218      +/-   ##
==========================================
+ Coverage   93.42%   93.43%   +0.01%     
==========================================
  Files          54       54              
  Lines        3771     3809      +38     
==========================================
+ Hits         3523     3559      +36     
- Misses        248      250       +2     

Flag	Coverage Δ
e2e	31.39% <23.07%> (-0.08%)	⬇️
integration	51.14% <33.33%> (-0.20%)	⬇️
unit	90.31% <94.87%> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[apify-factory]

Looks good, just one note.

🏭 Factory review — ℹ️ not auto-approved

This change was reviewed but cannot be auto-approved: a gate failed, so the review cannot end in an approval.

check	result
Static gates	❌ 14/16 — pr-open-and-ready, deny-globs
Review findings	❌ not clean
Reviewer escalation	❌ Changes pay-per-event charging limit accounting (money) and adds an API request to the charge path on platform runs.
Juror 1 — claude-sonnet-5-5, adversarial	⏭️ skipped — a gate failed

Why it was not auto-approved

Failed gates:

• pr-open-and-ready: PR is a draft
• deny-globs: src/apify/_charging.py matches src/apify/_charging.py

The comments above are the review itself; this section only explains the approval decision. Push a change and request @apify-factory again to re-run it, or ask a human to review.

_{Reviewed 896e79144 · workflow run}

[Pijukatel]

Hmm, platform's eventual consistency is too slow for this again :( , probably we will have to track it again ourselves