Skip to content

[BE-146] No load/soak test validates a full reconciliation pass fits inside its own cron interval #1701

Description

@yusuftomilola

Overview

ReconciliationService runs on @Cron(CronExpression.EVERY_5_MINUTES) and PAYMENT_RECONCILE_MAX_BATCH bounds one pass at 500 payments, but nothing tests that processing 500 real payments (with their outbound provider calls, even against a sandbox/mock) actually completes well within 5 minutes. If it doesn't, overlapping cron runs become a real risk.

Tasks

  • Add a load/timing test simulating a full PAYMENT_RECONCILE_MAX_BATCH-sized batch and asserting it completes within a safety margin under the cron interval.
  • If it doesn't comfortably fit, add explicit overlap protection (a run-in-progress flag or advisory lock, matching the pattern already used in SettlementService.lockAccount).

Acceptance Criteria

  • A full-batch reconciliation pass is proven to fit inside its cron interval, or explicit overlap protection exists.

Notes for Contributors

Comment below to be assigned.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions