Hi everyone,
it seems the log files I’m getting when using the command line parameter (savelog=xxx.log) are limited to about 32KB in size. When I open the log, the beginning is visibly missing. Is there a setting somewhere that makes the limit higher?
Thanks!
The &savelog= log file is indeed limited. It displays only the last 500 lines
plus the
Status=OK (or error message)
###
at the top. These two lines are the main purpose of the savelog log, so the RPA software can communicate its status back to the calling script.
This &savelog command line log should not be confused with the detailed macro execution log. You find it - in hard-drive mode - in the XModule /log folder.
See also Ui.Vision reporting options
Example of 500 lines max &SaveLog log:
Status=OK
###
[echo] i=877
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=878
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=879
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=880
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=881
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=882
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=883
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=884
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=885
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=886
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=887
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=888
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=889
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
(some lines removed here)
[echo] i=999
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | echo | i=${!times} | green |
[echo] i=1000
[info] Executing: | end | | |
[info] Executing: | times | 1000 | |
[info] Executing: | store | fast | !replayspeed |
[info] Executing: | dragAndDropToObject | id=one | id=bin |
[info] Executing: | dragAndDropToObject | id=two | id=bin |
[info] Executing: | dragAndDropToObject | id=three | id=bin |
[info] Macro completed (Runtime 492.18s)
Thank you admin for the reply!
Oh I see. I didn’t know it’s supposed to show only 500 lines by design.
I know about the log folder, but the logs there are a little bit difficult to read as it isn’t really clear in which file is which “playthrough”, as it’s bunched together into a single file and only when the RPA is closed the new log file is created.
What I like about the logs created by the “savelog” command is that I can use the powershell script to extract only the echoes and errors from them, and each playthrough of the macros has its own log file. It’s easier to find the information I need this way. So if there’s any chance you could easily make the 500 lines limit into 5000 would be cool 
Hi Everyone, What is the Maximum Limit of Auto logs generated in Hard drive?
Is there a limit for the number of logs? I don’t believe RPA checks how many logs there are already saved. But I could be wrong…
Hi, it is about maximum limit of Lines printed in Autogenerated Log (Hard-drive option)
Hi, there is no limit in the number of logs. If you encounter a “limit” in any way, that would be a bug.