Alex Moinet

I think this is fair, if environment variables are expected to configure options that should be respected in all environments. What do you think @GrahamCampbell?

Based on the discussion in this thread I'd suggest looking at @dominics [fix](https://github.com/bugsnag/bugsnag-laravel/issues/226#issuecomment-292824200) for now, and we'll schedule a discussion on this to see what we can do.

As indicated in the discussion there isn't really a good way of fixing this for us at the moment. I'd advice you to check out @dominics fix above for a...

Hi @dbpolito, I've confirmed your findings, and I'm glad you've found a workaround. However this may be an issue we end up documenting, unless we can think of a non-intrusive...

Hi @ragingdave, thanks for the feature request! I've raised it with our products team and we'll try and update you on when things progress. In the meantime, are you able...

You can also register a callback in a specific controller so that the callback would only be added when the routes that receive the XML/SOAP data is called.

I'm closing this for now, but I'll update it as the feature request progresses. _Edit - We're going to keep this open as a place to reference as progression for...

Hi @woutersamaey, it seems this would interfere with our retrying logic that would generally trigger to split up large payloads. While I understand having a singular payload event that's too...

I agree, that doesn't sounds ideal at all. I think adding a failure condition with full logs would be a practical way to approach this as suggested, and I'll suggest...

Hi @jeroensmit, thanks for the feedback, I'll raise this ticket to our products team to consider.