[vladfrangu]

Actor.set_status_message() no longer raises when the run update fails. It logs a warning and returns None, the same value it returns locally, and abandons an update that takes longer than one second. This matches the JavaScript SDK (apify/apify-sdk-js#807).

• The missing-run-id RuntimeError on the platform is kept, since it marks a broken environment rather than a transient API failure.
• The exit() guard around the terminal status message is untouched.
• Unit tests cover the successful, failing and timed-out update paths.
• Upgrading guide has a short subsection.

BREAKING CHANGE: Actor.set_status_message() returns None instead of raising when the run update fails or times out, and logs a new warning Failed to set status message for Actor run with ID "...".

Closes #1199

[🤖] Claude Code using Fable 5.1

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.42%. Comparing base (4ff9c35) to head (8814b45).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1200      +/-   ##
==========================================
+ Coverage   93.25%   93.42%   +0.16%     
==========================================
  Files          54       54              
  Lines        3766     3771       +5     
==========================================
+ Hits         3512     3523      +11     
+ Misses        254      248       -6     

Flag	Coverage Δ
e2e	31.47% <14.28%> (-0.05%)	⬇️
integration	51.33% <14.28%> (-0.07%)	⬇️
unit	90.26% <100.00%> (+0.17%)	⬆️

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.

[vdusek]

Well, if we do it now, it can't be marked as breaking ("fix!").

[Pijukatel]

Feels more like a breaking change of behavior for next major release, not a fix.

[vdusek]

Closing this, @vladfrangu feel free to reopen it if you find a way to make this non-breaking.

[vdusek]

After an internal discussion, we're treating this as a non-breaking fix for a regular patch/minor release. The only code it could break is code that catches the exception set_status_message() raised on a failed update, and we don't expect anyone to rely on that. LGTM, merging.