Skip to content

Exclusions are not handled as expected in mark call and code needs optimization #1301

@ppratikcr7

Description

@ppratikcr7

Version where bug was found:
e.g "5.1.0"

Describe the bug
Currently the various exclusions codes are not stored in the DB for simple and within subject experiments. Mark call code for exclusions needs optimization to not call various code blocks for all experiment state. We are also storing multiple rows for Individual Enrollments for within subject experiments and we are also storing multiple rows for monitored decision point table for experiment level exclusions.

To Reproduce
Steps to reproduce the behavior for few exclusions, or refer to the detailed document for all exclusion codes:

  1. Try to exclude a user who is on exclusion list using a segment or individual exclusion list.
  2. Once you hit /mark api for the user, you wont see its Data as the table is not getting populated with the reason for exclusion.

Expected behavior
Exclusions should work as expected for the above scenario.

Metadata

Metadata

Labels

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions