Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0
-
Fix Version/s: 3.3.2
-
Component/s: None
-
Labels:None
Description
When the cron processes renewals for services, it may not fetch any services that are renewable and paid (which thus renew). This appears to be because it filters on a past date, but that past date is not from the previous task run date (~5 minutes ago), but rather the current time.
So, only services whose invoices have been closed in the same second as this task's execution would be renewed. However, the incorrect date is used to determine renewals, which can cause some to experience multiple consecutive renewals.
This can cause module renewals to not be triggered, or to be triggered too often for the same service. Renew dates still get bumped, as they are separate from this action.
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Description |
When the cron processes renewals for services, it may not fetch any services that are renewable and paid (which thus renew). This appears to be because it filters on a past date, but that past date is not from the previous task run date (~5 minutes ago), but rather the current time.
So, only services whose invoices have been closed in the same second as this task's execution would be renewed. This causes module renewals to not be triggered. Renew dates still get bumped, as they are separate from this action. |
When the cron processes renewals for services, it may not fetch any services that are renewable and paid (which thus renew). This appears to be because it filters on a past date, but that past date is not from the previous task run date (~5 minutes ago), but rather the current time.
So, only services whose invoices have been closed in the same second as this task's execution would be renewed. However, the incorrect date is used to determine renewals, which can cause some to experience multiple consecutive renewals. This can cause module renewals to not be triggered, or to be triggered too often for the same service. Renew dates still get bumped, as they are separate from this action. |
Tyson Phillips (Inactive)
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |