You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Logs: Not sent when there are always logs being collected under the flush timeout #18204
letcounter=0;constsender=()=>{Sentry.logger.info(`never flushed number ${counter}`);setTimeout(sender,2000);};sender();
Steps to Reproduce
run the snippet code and you will notice that even after minutes there will be no logs in spotlight/sentry
Expected Result
logs being captured
Actual Result
no logs being captured.
Additional Context
I read the client code on the latest commit and it seems the same as the one that presents the issue.
The main problem is for every log captured, the flush timeout is reset to a new timeout delay.
If we have a constant inflow of logs, we will never send those logs.
EDIT: It seems like it's actually sent, but only when we reach 100logs, meaning that the sample loop takes 2 minutes and 33 seconds before sending it.
spotlight tricked me in thinking the logs were partially sent but all of them were correctly sent at sentry.io
Activity
linear commentedon Nov 14, 2025
JS-1163
lucas-zimerman commentedon Nov 14, 2025
Similar to getsentry/sentry-react-native#5378 since we use the same flush logic.
andreiborza commentedon Nov 14, 2025
Hi @lucas-zimerman, thanks for writing in.
Yea, we reset the flush timeout every time a new log comes in which means you'll be able to delay the flushing by quite a bit with slow-logging.
We'll switch to not reset the timeout as new logs come in and flush earlier, thanks again for bringing this up!
fix(core): Fix log flush timeout starvation with continuous logging
fix(core): Fix logs and metrics flush timeout starvation with continu…
github-actions commentedon Nov 19, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #18211, which was included in the 10.26.0 release.