Validation: Do not allow defined activity with zero amount #176
Labels
good first issue
Good for newcomers
Robustness
Changes that improve the robustness of running the simulator
Milestone
Currently, we allow zero amount payments to be skipped over to allow for the possibility that our random payment amount generation spits out a zero value every once in an hour.
Right now we don't validate that we're provided with a non-zero defined activity amount, so we'll hit the same check and just endlessly not dispatch payments if we're given a zero value.
We should update validate_activity to disallow zero values.
The text was updated successfully, but these errors were encountered: