Describe the bug
When I save to state and publish an event, I get this error infrequently. Sometimes it happens, other times, the code works as intended.
I'm not using the OUTBOX pattern
{ "detail": "<_InactiveRpcError of RPC that terminated with:\n\tstatus = StatusCode.UNAVAILABLE\n\tdetails = \"upstream connect error or disconnect/reset before headers. reset reason: connection termination\"\n\tdebug_error_string = \"UNKNOWN:Error received from peer {grpc_message:\"upstream connect error or disconnect/reset before headers. reset reason: connection termination\", grpc_status:14, created_time:\"2024-08-27T10:00:15.692326+01:00\"}\"\n>" }
Describe the bug When I save to state and publish an event, I get this error infrequently. Sometimes it happens, other times, the code works as intended. I'm not using the OUTBOX pattern
{ "detail": "<_InactiveRpcError of RPC that terminated with:\n\tstatus = StatusCode.UNAVAILABLE\n\tdetails = \"upstream connect error or disconnect/reset before headers. reset reason: connection termination\"\n\tdebug_error_string = \"UNKNOWN:Error received from peer {grpc_message:\"upstream connect error or disconnect/reset before headers. reset reason: connection termination\", grpc_status:14, created_time:\"2024-08-27T10:00:15.692326+01:00\"}\"\n>" }
To Reproduce Here's the repo https://github.com/trey-rosius/group-chat-microservice/tree/main Run the application and make this post request.
/v1.0/state/groups/{group_id}/participants'
You'll have to setup a pub-sub AWS broker and a state.
Expected behavior I expected the item to save and then publish the event successfully without throwing any errors.
Screenshots
Additional context