Summary
If a membership payment collection (via direct debit) fails, FLOW has a payment setting to retry to take the payment which can be configured in the System Configuration module. It's defaulted to '2' on the system but it can be amended to cater to your needs. If you don't want the system to retry and collect the money and would prefer that after one failed attempt, the membership goes through the cancellation process, please set it to '0'.
The fee will usually be generated and sent to GoCardless around 10 working days before the due collection date and will remain on hold until then.
When the first collection is successful, the date displayed in the 'Updated At' column is the next working day after the billing date.
When a payment comes back as unsuccessful, it will send a new request to collect to GoCardless on that same day. The first re-try will happen one working day after the billing date. From the second failed collection, it takes roughly 4/5 working days before retrying again as that's the time it takes to update FLOW with the new failed status.
Example of a successful collection:
Billing date: 1st of the Month.
You can see that the fee was generated and sent to GoCardless 10 working days before the billing date in the 'Attempted At' column whilst the date in the 'Updated At' column is one working day after the billing date.
If failed, it will usually show in the 'Updated At' column
Example of an unsuccessful collection:
Billing date: the 1st of the Month.
You can see from the screenshot below that the 1st collection came back as failed (insufficient funds, cancelled mandate, etc...) and the date showing in the 'Updated At' column is the second of that same month (one working day after the billing date).
On the same day, FLOW sent a new attempt to collect to GoCardless. The payment came back unsuccessful again 4/5 working days later and FLOW sent another attempt to collect to GoCardless and so on...