Skip to content

fix!: swallow and warn when setting the status message fails - #1200

Open
vladfrangu wants to merge 1 commit into
masterfrom
fix/set-status-message-swallow
Open

vladfrangu wants to merge 1 commit into
masterfrom
fix/set-status-message-swallow

Conversation

@vladfrangu

Copy link
Copy Markdown
Member

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

`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).

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
@vladfrangu
vladfrangu requested a review from szaganek as a code owner October 21, 2026 09:08
@github-actions github-actions Bot added the t-tooling Issues with this label are in the ownership of the tooling team. label Oct 21, 2026
@apify-service-account apify-service-account added the tested Temporary label used only programatically for some analytics. label Oct 21, 2026
@codecov

codecov Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.29%. Comparing base (7d2a7b7) to head (853e2c0).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1200      +/-   ##
==========================================
+ Coverage   89.89%   93.29%   +3.39%     
==========================================
  Files          54       54              
  Lines        3691     3698       +7     
==========================================
+ Hits         3318     3450     +132     
+ Misses        373      248     -125     
Flag Coverage Δ
e2e 31.58% <21.42%> (-0.01%) ⬇️
integration 51.56% <21.42%> (?)
unit 90.07% <100.00%> (+0.18%) ⬆️

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-tooling Issues with this label are in the ownership of the tooling team. tested Temporary label used only programatically for some analytics.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

setStatusMessage() should swallow the error when the update fails

2 participants