Bot triggers second allocation review hours after the first - should be after 75% usage

[kevzak]

Here are two examples where the initial allocation is approved, and the bot creates an "Application Granted" and "Application in Refill" comment together and triggers the next allocation request.

There is no way the client used 75% of DataCap to trigger next request.

Two examples:

MikeH1999/RFfil#3 (comment)

fidlabs/Enterprise-Data-Pathway#3 (comment)

[kevzak]

Also - the second request was for 512TiB. Is this where allocation algorithm is coming from? https://github.com/filecoin-project/filecoin-plus-large-datasets?tab=readme-ov-file#datacap-tranche-size-calculations

separate request: we need clarity on allocation algorithm and ability to edit.

MikeH1999/RFfil#3 (comment)

[kevzak]

Seems like these clients are using the same addresses from older LDN applications. The usage of the same address across applications likely causes issues in allocation calculations and reminders.

[Lind111]

Lind111/EF#9 (comment)

I also encountered a similar issue here, which triggered again one hour after manually signing ready to sign
The client is a new address