Recurring Globalcollect: only mark subscription as failed if it was a processor failure
Open, LowPublic
Actions

Assigned To

None

Authored By

	• atgo
	Jul 29 2015, 11:29 PM

Description

Copied from Mingle

There are lots of things that might fail, e.g. we cannot contact the server. This is not a charge failure, and should not affect the subscription record. Currently we treat any exception as if it were an API failure.

Event Timeline

• atgo created this task.Jul 29 2015, 11:29 PM

• atgo raised the priority of this task from to Low.

• atgo updated the task description. (Show Details)

• atgo added projects: Recurring-Donations, Fundraising-Backlog-Old, Fundraising-Backlog.

• atgo removed a project: Fundraising-Backlog-Old.

• atgo set Security to None.

• atgo added subscribers: • atgo, Aklapper.

• atgo moved this task from Triage to Old Unscheduled (prior to 2019) on the Fundraising-Backlog board.Jul 29 2015, 11:36 PM

• atgo moved this task from Backlog to Features on the Recurring-Donations board.Jul 30 2015, 12:12 AM

• atgo unsubscribed.Mar 30 2016, 10:07 PM

Recurring Globalcollect: only mark subscription as failed if it was a processor failureOpen, LowPublicActions

Description

Event Timeline

Recurring Globalcollect: only mark subscription as failed if it was a processor failure
Open, LowPublic
Actions