Skip to content

Event Batching doesn't seem to be enabled by default #313

Closed
@wired9

Description

@wired9

We have found that if a feature is a part of experiment, Optimizely sends a blocking API call to send an impression event every time a decision is made. Your doc here: https://docs.developers.optimizely.com/full-stack/docs/event-batching-ruby says that BatchEventProcessor is enabled by OptimizelyFactory.default_instance, however, an instance of ForwardingEventProcessor seem to be actually used.

We're using v3.6.0, upgrading to 4.0.0 shows the same.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions