CLI - recurrent transfer
- Create a recurrent transfer:
a. Command:
clive process transfer-schedule create
b. Parameters:
- from - required (may be default from profile)
- to - required
- amount - required
- memo - optional
- pair_id (from HF28)
- frequency (reccurence) - required
- repeat (executions) - required
c. Validations:
- executions >1
- frequency >= 24h
- The maximum time a recurrent transfer can exists is 730 days (2 years)
- if the recurrent transfer with the same
from
andto
exists, there should be an error (something likes: it is impossible to create a recurrent transfer, because a recurrent transfer already exists. You can remove or modify existing recurrent transfer).
- Modify a recurrent transfer:
a. Command:
clive process transfer-schedule modify
b. Parameters:
- from - required (may be default from profile)
- to - required
User may change:
- amount
- frequency (reccurence)
- repeat (executions)
- memo
c. Validations:
- executions >1
- frequency >= 24h
- The maximum time a recurrent transfer can exists is 730 days (2 years)
- amount >0 (if a user wants to remove a recurrent transfer, he should use a remove)
- Remove a recurrent transfer:
a. Command:
clive process transfer-schedule remove
b. Parameters:
- from - required (may be default from profile)
- to - required
c. Validations:
- a recurrent transfer exists
-
General remarks (somewhere in Help)
a. The first transfer is executed immediately.
b. The exchanges don't support recurrent transfers.
c. If the first transfer fails because of the lack of funds, it will not be automatically repeated -
Show
a. Command:
clive show pending transfer-schedule
b. to show:
- from
- to
- amount
- memo
- next recurrent transfer (w API trigger_date)
- frequency (w API recurrence)
- remaining_executions (how many more times should be executed, there is no information how many times the transfer was already executed. )
- consecutive_failures (consecutive failed executions - important because after 10 times it stops execution)
Edited by Aleksandra Grabowska