Question

Photo of Kjell Nygren

0

Answered: 5.4 NMI scheduled transaction issue

2

I'm at a loss for how to troubleshoot this further, but something's broken, and I don't know how to fix it.


It was brought to my attention yesterday, that scheduled transactions haven't been imported from Transnational for several weeks. We are receiving single transaction, so I know that our gateway settings are correct. On 5.3, the transactions would be imported and marked as inactive. Scheduled transactions are received by the gateway, and are successfully processed at the proper time. But they never end up appearing in Rock.


After looking at the missing transactions, we figured out that it's been like that ever since we ran the 5.4 update. I've double checked the job process and it's happening. I've tried to manually kicking the job via date range in the finance section. They just aren't getting pulled.


Kind of a big deal. What do we do?

---

Something happened between 5.3 and 5.4. Either the password wasn't getting checked, or we had the wrong password entered. Changed the password to the correct one and it started working. We still had many transactions marked as inactive that were actually active. David Turner helped me out by giving me a SQL query to update those. Here's the query, use at your own discretion. It worked for us in changing the status of 26 transactions. There were a couple that it didn't fix that may have fallen outside of the 30 days that it checks.

UPDATE S SET [IsActive] = 1 
FROM [FinancialTransaction] T 
INNER JOIN [FinancialScheduledTransaction] S
      ON S.[Id] = T.[ScheduledTransactionId]
WHERE S.[IsActive] = 0 
AND DATEDIFF( day, T.[TransactionDateTime], GETDATE() ) < 30
  • Photo of David Turner

    0

    Just to summarize the resolution of this. Rock version 5.3 had an issue that would result in NMI scheduled profiles getting marked incorrectly as inactive. That was fixed in v5.4. For the few churches that were using NMI prior to 5.4 we have manually corrected those profiles. Regarding the issue of transactions not being downloaded. In each case it was an issue of incorrect or invalid username password. Aaron's password had a special character ('%') that did not work in v5.4 of Rock. Version 6.1 includes a fix so that special characters will work, but Aaron has changed his password for now. V6.1 also includes an update that will report more accurately that the username/password is incorrect.

  • Photo of Jim Michael

    0

    I would enter this as a bug. Sounds like you've narrowed it down to the 5.4 update and at least this will  put in on the radar for a response.  https://github.com/SparkDevNetwork/Rock/issues?q=is%3Aopen