Aaron McCausland
05/01/2026, 4:37 PMCeligo AI
05/01/2026, 4:37 PMAI generated answer (using internal Slack threads):To find and resolve errors that caused Memorized Transactions to change from Automatic to Reminder mode, and then make them run again to see if the error is really fixed and make the real transaction record get created, you can follow these steps: 1. Identify the Error: The first step is to identify the error that caused the Memorized Transaction to switch from Automatic to Reminder mode. This can be done by checking the error message that was generated when the transaction failed to run automatically. 2. Resolve the Error: Once the error has been identified, the next step is to resolve it. This could involve several steps depending on the nature of the error. For example, if the error was due to a mandatory field (like the Reference Number field) not being filled, you could set up a workflow to automatically fill this field upon the creation of the transaction. If the error was due to an incorrect tax code, you would need to edit the transaction that's the template to update the tax code, and then rememorize it. 3. Test the Solution: After resolving the error, you should test the solution to ensure that it works. This can be done by setting the Memorized Transaction back to Automatic mode and then running it to see if it now works correctly. If the transaction runs successfully and the real transaction record gets created, then the error has been resolved. If not, you may need to revisit the error and try a different solution. 4. Monitor the Transaction: Finally, after resolving the error and testing the solution, you should monitor the Memorized Transaction to ensure that it continues to run correctly in Automatic mode. If the transaction switches back to Reminder mode, this could indicate that the error has not been fully resolved and further action may be needed. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Celigo AI
05/01/2026, 4:37 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.821289062
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.821105957
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.813171268
Celigo AI
05/01/2026, 4:37 PM