[$30] Inconsistency in payment step between Scheduler and WorkPeriodPayment table

[maxceem]

When scheduler processes the payment if it fails, then details about the error are stored in the WokrPeriodPayment table:

{
        "amount": 3.68,
        "updatedBy": null,
        "billingAccountId": 80000071,
        "workPeriodId": "c0c613e3-845a-45c0-85fe-41c063d9df3d",
        "createdAt": "2021-06-18T06:51:07.303Z",
        "challengeId": null,
        "memberRate": 18.4,
        "createdBy": "57646ff9-1cd3-4d3c-88ba-eb09a395366c",
        "customerRate": 84.88,
        "days": 1,
        "statusDetails": {
            "challengeId": "9394992c-fd94-444d-9943-583babe0a5c3",
            "errorMessage": "Cannot Activate this project, it has no active billing account.",
            "errorCode": 400,
            "step": "activate-challenge", // <---------------------------------------------------------
            "retry": 1
        },
        "id": "a397d4bb-cd72-413f-b430-95effa7220a2",
        "status": "failed",
        "updatedAt": "2021-06-18T06:51:41.609Z"
    },

The same time the data is stored in the PaymentScheduler table. But in some reason for all the failed steps it stores that failed step is close-challenge:

So there is inconsistency:

• in WorkPeriodPayment table the failed step is activate-challenge which looks correct as per error
• in PyamentScheduler table the failed step is close-challenge which sounds incorrect as per error, but maybe it could be veice verse

[maxceem]

hi @xxcxy would you like to have a look on this issue?

[maxceem]

Paid via https://www.topcoder.com/challenges/e32317b8-9062-4279-a6c2-60f6e799fe82