New error -- old problem

Last week's CiviCRM upgrade (and related updates) generated a couple of questions from clients who, quite naturally, guessed that it was causing problems.

That's because, after the upgrade, they started seeing error messages they hadn't seen before.

One example:

The Stripe extension started reporting that some payments were recorded in Stripe but not completed in CiviCRM.

On investigation, we found that the payments in question were from over a year ago.

The problem has existed for over a year.
But the Stripe extension hasn't been reporting on it --
until we upgraded it for security reasons (as recommended by the CiviCRM upgrade announcement).

So instead of bad news (“the upgrade is causing new problems”) this was good news:
a problem that has gone unseen for over a year has now become visible.

That means we're able to identify it, understand it, and take action to clean up the data.

So:

Seeing a new error message doesn't always mean you've got a new problem.

Sometimes it just means the error detection has improved.

That's a good thing!

All the best,
A.

Next
Next

How? Or, why?