Skip to content

bulk data load being identified as recursive transactions #40

Open
@sfdevarch17

Description

@sfdevarch17

When implementing the setMaxLoopCount from the individual handlers, the loop count gets incremented after the first chunk of 200 records are processed as it identifies the subsequent set of records as recursive transactions. Need to identify a way around that by comparing the old set of records with the new ones and if it doesn't match, then not to increment. Else identify the correct way to clearMaxLoopCount.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions