Source: github.com/e2b-dev/E2B/releases/tag/%40e2b%2Fpython-sdk%402.63.0
The release adds a strict flag to pause(), which defaults to false. When strict is set to true, a pause call fails with a ServiceBusyError or ServiceBusyException if the guest agent does not respond, and the sandbox stays up.
Without the flag, the API's default behavior applies: the memory snapshot is taken anyway and marked. The sandbox info exposes this mark as envd_unresponsive_at_pause, and resuming such a sandbox with on_resume set to "reboot" now raises GuestUnresponsiveException.
The change is listed as a minor change in the 2.63.0 release, which was published on 04 Nov.
Why it matters if you build agents
Agent code that pauses sandboxes can now choose to fail fast instead of snapshotting a sandbox whose guest agent is unresponsive.
Code that resumes paused sandboxes with on_resume="reboot" should handle GuestUnresponsiveException, since such resumes now raise it when the pause was marked.
Get stories like this every weekday
One short email with the day's agent tooling news.