Open serglom21 opened 1 month ago
Hi @serglom21, thank you for the message,
I agree, it doesn't sound right, that these transaction are marked as deadline_exceeded
. I'll take a look at the examples and keep you updated.
Are you using something on the screens with deadline_exceeded
a code called Stack.Navigator
to switch between different pages? You can usually find it by looking for the term
Are you using something on the screens with
deadline_exceeded
a code calledStack.Navigator
to switch between different pages? You can usually find it by looking for the termin your code
Yep, we are using the Stack.Navigator
.
Hi, I found a potential fix for your case and a solution will be implemented soon on the SDK.
Hi, I found a potential fix for your case and a solution will be implemented soon on the SDK.
@lucas-zimerman thanks a lot for it, we are expecting to solve this issue ASAP to normalize our failure_rate
metrics. When you had an stable version with the fix, could you share it here, pls?
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.22.0
react-native
version: 0.72.3Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
I have the following issue:
I am seeing some inconsistencies in the data reported and what should be reported based on the SDK behaviour. For example, it is odd to me that some transactions are being marked as 'deadline_exceeded' when they do not exceed the default value for [finalTimeoutMs].
finalTimeoutMs
is also not being overridden in the init code blockThe default for
finalTimeoutMs
is 600000ms or 10mins, which is way above what the transactions being marked deadline_exceeded are reporting. The amount of failed transactions with this status seems to have increased after updating the SDK version from5.3.0
to5.22.0
More details with links to examples in the Customer Case