By Grzegorz Szyszka on Wednesday, 20 May 2020
Posted in General
Replies 5
Likes 0
Views 0.9K
Votes 0
I created recurring subscription with 5 minutes validity time

It was activated at 1:45 (see attached screenshot of invoices)
Then I did not touch the website so that automated cron tasks would not start
Next subscriptions were created only after cron activation (see invoice hours)
For invoices this is OK because it is not so important that they are created immediately
However, the hours of successive subscriptions were also calculated from the moment of activation of the cron (see the second screenshot and the final time of subscription validity)
It looks like you are mistakenly counting the activation time of the next subscription as added to the current time and not to the end date and time of the previous subscription
For first occurrence its ok but not for next ones
This caused the subscription to have an validity time of 3:26 instead of 2:00
So it lasted 5 times longer than it should!
Assuming that we do not use automatic cron but run it on the server, however, this mechanism causes large errors in calculations, especially for micro-subscription
Hey,

In case of recurring payment, after initial payment all the further recurring payment done on cron job. When cron job run , it will request for the payment , when payment done , subscription expiration time will extend from the time when invoice actually paid.
This is flow of payplans recurring subscription extension.

In your case if you want to use micro subscription then you need to make sure that your cron should run on time.
In case auto run, it would replay on frontend access. We recommend to setup the cron on server. In case you have micron subscription then you should set the cron frequency accordingly.

Looking foreword to your response.

Thank you for understanding !
·
Wednesday, 20 May 2020 19:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Run cron on server as often as possible do not solve this problem
Only limits impact
Shortest time which I can run cron on server is 5 minutes
Anyway problem will appear but with smaller scale

In my opinion its should be changed as I described

I do not plan to use microsubscriptions on mi site and generally this bug will nit hurt me
I just describing it for your info and you will decide what to do with it, because for microsubscriptions its produces significant errors even if cron runs on server every 5 minutes.
·
Wednesday, 20 May 2020 19:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey,

Thank you for sharing your suggestions.
Well currently it's not possible to change the workflow as it will create significant impact on this.
I'll discuss with this team regarding this.

Thank you for understanding !
·
Thursday, 21 May 2020 10:50
·
0 Likes
·
0 Votes
·
0 Comments
·
As I said
This problem is only critical for short payment periods
I think it is worth entering it for change at a convenient time.
·
Thursday, 21 May 2020 17:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you for sharing your suggestion on this.
·
Thursday, 21 May 2020 17:43
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post