Sending events from application returns error but events are saved in sentry

Hi,
I am sending test events from the application. When I do that I get the following response.

Unable to record event with remote Sentry server (Sentry::Error - execution expired):
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/transport/http_transport.rb:29:in `rescue in send_data'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/transport/http_transport.rb:15:in `send_data'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/transport.rb:31:in `send_event'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/client.rb:95:in `send_event'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/client.rb:47:in `block in capture_event'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/background_worker.rb:33:in `block in perform'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:353:in `run_task'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:342:in `block (3 levels) in create_worker'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:325:in `loop'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:325:in `block (2 levels) in create_worker'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:324:in `catch'
Failed to submit event. Unreported Event: RuntimeError: This raise an error for sentry.
Unable to record event with remote Sentry server (Sentry::Error - execution expired):
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/transport/http_transport.rb:29:in `rescue in send_data'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/transport/http_transport.rb:15:in `send_data'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/transport.rb:31:in `send_event'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/client.rb:95:in `send_event'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/client.rb:47:in `block in capture_event'
/home/mason/.rvm/gems/ruby-2.6.5/gems/sentry-ruby-core-4.2.2/lib/sentry/background_worker.rb:33:in `block in perform'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:353:in `run_task'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:342:in `block (3 levels) in create_worker'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:325:in `loop'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:325:in `block (2 levels) in create_worker'
/home/mason/.rvm/gems/ruby-2.6.5/gems/concurrent-ruby-1.1.6/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:324:in `catch'
Failed to submit event. Unreported Event: <no message value>

but the strange thing is, i can see the events on sentry.
Can someone please let know or tips on how to debug the issue. I do not see any kind of error or exceptions on the logs in any of the components.

Update:

I have tried to send test events with curl and it works.

* Connection #0 to host sentry.xxxxx.com left intact
{"id":"1fb292db36ae4bf4a96298c7ca85ca47"}

The conclusion then is, there is something wrong with the client library. Can you please look into it ?

regards

Can you report this in the SDK repo then: https://github.com/getsentry/sentry-ruby/issues/new?assignees=st0012&labels=bug&template=bug_report.md&title=

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.