Scheduled Reminders one stopped

[johnd]

We have about 30 scheduled membership reminders setup and working well on 4.4.3. Except two just stopped working.

While all the others continue to work, both of the failed reminders were set for 1 month after membership expiration date and they both stopped working after 31 July 2014.

I checked the Scheduled Jobs log and mail is otherwise all working.

So I deleted the two that didn't work and re-created them from scratch, this time with 30 days instead of 1 month after membership expiration. They are still the only reminders that won't send.

There is no limitation group used.

The template contains basic HTML and one external image.

What should I look into next?

[johnd]

Scheduled reminders started working again in our case (CiviCRM 4.4.3) once we removed the membership status of "Grace".

So, we knew that scheduled reminders must exclude subscriptions marked 'Deceased', 'Cancelled' and 'Pending'... but they also exclude 'Grace' - in our use case, this was a bug, not a feature.

See also: https://issues.civicrm.org/jira/browse/CRM-12219

Also, the documentation has a few contradictions:
- Is says memberships statuses can be selected, I can't do this even on the demo site
- It gives a membership reminder example using 'Pending', which I understand won't work

http://book.civicrm.org/user/current/email/scheduled-reminders/

[Eileen]

That seems like a bug to me too - presumably it is excluding it's not excluding by name but because of some 'feature' of that status - what does your membership_status table look like (if you can export as a format that will paste in here in a readable way)

[ojkelly]

H Eileen,

Here's the table as it is currently. Grace is disabled in this table. When it was enabled the only difference was

Code: [Select]

is_active = 1
I'm inclined to think the issue is that Grace status

Code: [Select]

is_current = 0might have been causing the issue. But I have not delved into the code of scheduled jobs to find out more.

id	name	label	start_event	start_event_adjust_unit	start_event_adjust_interval	end_event	end_event_adjust_unit	end_event_adjust_interval	is_current_member	is_admin	weight	is_default	is_active	is_reserved
1	New	New	join_date	NULL	NULL	join_date	month	3	1	0	1	0	1	0
2	Current	Current	start_date	NULL	NULL	end_date	NULL	NULL	1	0	2	1	1	0
3	Grace	Grace	end_date	NULL	NULL	end_date	month	4	0	0	3	0	0	0
4	Expired	Expired	end_date	month	4	NULL	NULL	NULL	0	0	4	0	1	0
5	Pending	Pending	join_date	NULL	NULL	join_date	NULL	NULL	0	0	5	0	1	1
6	Cancelled	Cancelled	join_date	NULL	NULL	join_date	NULL	NULL	0	0	6	0	1	0
7	Deceased	Deceased	NULL	NULL	NULL	NULL	NULL	NULL	0	1	7	0	1	1
8	On hold	On hold	join_date	NULL	NULL	join_date	NULL	NULL	0	0	8	0	1	0

[Eileen]

I think that if Grace is inactive you have no valid status between the end date & 4 months later when expired kicks in looking at the above table

[joanne]

@johnd
You are right that the membership status is not something you can select if you choose the Entity membership and I will remove that from the documentation.

However, the example for sending a reminder to people with a pending membership is valid. As stated, it runs off the activity entity not the membership entity.

@ojkelly
I suspect in you are right in assuming that is_current = 0 for the Grace status caused your problem.  We have scheduled reminders going successfuly to members with the status Grace but we have is_current = 1 for our grace status.