Automation Log and Processing do not match
Running a solution of automations that have worked in the past. The automation log, and behavior of the automtation suggest that large portions of the automations, and called automations, are not processing.
In the attached screen grabs, MASHER START, nor any of the variable initializations, nor the LEVEL 1 Create Model Mappings show up in the log. In fact, the Masher automation does not show in the logs -- the ReadNotes is the first automation to show log entries and it is 3 calls deep. Further, there are csv writes that should be occuring but do not, suggesting large parts of the code are skipped.
- 19 replies
- Thomas Parker @mrtopkid2021-05-14 11:30:05.046Z
I can see in the log that the message that looks like it's supposed to go to the masher automation, is going to dbo.notes? I can also see from your reply that it has not been set that way. Perhaps there is an automation ID conflict.
Could you try creating a new automation, copying the code from masher and sending to that new test automation please?
- SStephen Parker @stephenparker2021-05-14 12:15:22.774Z
I've done a quick test with multiple levels and it is working ok in my test.
Test SQLite DB: 2 Tables : Departments(ID,Name) and Persons(ID,Name,Age,Email,Dept)
Its shows the correct sequence in Log/Notifications.
Would you be able to export the Solution for us to take a look?
- SStephen Parker @stephenparker2021-05-14 14:02:26.280Z
Thanks - I've checked it - looks like the Call link on Masher Automation is lost. When you double click the Call actions it should display a preview.
You would need to open these call actions and reselect the correct automations. Open all the Call actions on all the Automations to make sure the preview isnt blank - if it is - reselect the correct Automation from the dropdown.
Possibly what has happened is the called automation has been deleted/cut and re-added and its lost the link in the Automations that call it. The Automations are called by their id - not name.
We will change the Studio so it doesnt allow deletion of an Automation that is being called somewhere else.
- SStephen Parker @stephenparker2021-05-14 15:53:26.890Z
We have posted an update. The latest version of the Studio will now prevent Automations from being deleted if they are Called other Automations. The Actions view will also show "NO AUTOMATION!" against the Call action where the Automation no longer exists (although this shouldnt happen going forward).
Ok I have downloaded update to 5.0.585.2 and reverified that all of the calls are properly linked. Automation ran in 1.296 seconds up from .916 seconds but very similar log results. There are several lines in teh log from Process dbo.Notes Row before ReadNotes now.
By chance I looked at the ThinkAutomation program data folder and see some very large error message logs that were last updated on 3/30/2021. Safe to delete these and do you think their size may have a bearing on some internal error reporting TA is attempting?
- SStephen Parker @stephenparker2021-05-14 17:25:14.735Z
Yes its safe to delete logs at any time - although those look like TA4 logs - not TA5.
- SStephen Parker @stephenparker2021-05-15 07:06:00.472Z
I've identified another issue with Importing a solution file causing the Automation Call links to break. Will fix this and then recheck your Solution.
Hi Stephen, I'm going to send another solution package after some of my own debugging. I'm still experiencing the issue, even after uninstall/reinstall TA5 version 585. But I've observed a couple of things. First, teh Automation Results window in the first automation does provide a complete log, including the list of records it finds in the database query. Second, I am getting the sense the Automation Process Log simply skips some entries. I haven't found a pattern, however, some of the new comment/log entries I make do end up showing up. Could I be experiencing a SQL table overload even tho I am clearing the server log between runs?
- SStephen Parker @stephenparker2021-05-18 10:40:26.715Z
Hi.. We have posted another update (589). If you use the Send Message option to send a test message - the comments displayed in the results view will now show all levels (including Called automations). Previously this only showed the top level Automation.
Its unlikely to be SQL overload - since the TA server queues up log lines.