I’ll start.
My company uses Authorize.Net and QuickBooks. There’s a process that used to run daily that would pull all the transactions from Authorize.Net, process/match them against records in our internal system, and then post them as transactions in QuickBooks.
It was developed by a previously used software company, and I never really touched it too much until it started randomly failing. If it failed to run, it seemed like future attempts would fail as well, so I would have to point my code to production endpoints and run it manually. After that, the normal process would seem to work fine for a few weeks at a time.
I’m assuming due to increases in the number of transactions we do over time, as well as the application probably querying more than it needs too, it’s gotten to the point where it won’t run on its own at all. I don’t have time to run it manually every day, so I just run it once a week to get the previous week’s transactions, or whenever my boss pings me, because I forgot…
I know that it’s something that I need to sit down and figure out exactly what’s so slow, but it’s easier to just think about running it once a week. But it’s getting to the point where it’s even timing out on my machine sometimes…
Maybe next week…
submitted by /u/lucidspoon
[link] [comments]