Skip to content

invocation suspension on google cloud run causes 502 error #98

@muhamadazmy

Description

@muhamadazmy

While running a load test with restate and cloud run I ran into the following scenario:
First of all, I noticed that the rust sdk logs a warn on suspension even if the user service is running locally. The suspension was triggered because of a low inactivity timeout

2026-02-18T08:59:53.574702Z  WARN restate_sdk_endpoint_handle{rpc.system="restate" rpc.service="Doss" rpc.method="entrypoint" restate.sdk.is_replaying=false}: restate_sdk::endpoint::futures::handler_state_aware: Error while processing handler Error when processing the request: Error { code: 599, message: "Suspended invocation", stacktrace: "", related_command: None, next_retry_delay: None } rpc.system="restate" rpc.service=Doss rpc.method=entrypoint
2026-02-18T08:59:53.574781Z  WARN restate_sdk::endpoint: Handler failure: Error(VM(Error { code: 599, message: "Suspended invocation", stacktrace: "", related_command: None, next_retry_delay: None }))

However even with this suspecious warning, the invocation always ran to completion on local setup.

When hosting the same service on cloud run, suspension caused restate to receive a 502 Bad Gateway error. The suspension was also triggered by the inactivity timeout.

When implementing the exact same service with the typescript-sdk, we had no issue with the test service running on cloud run, which make me suspect that the the warn from the rust sdk might indicate a bad handling of suspension.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions