Skip to main content
Русский

What can we help you with?

Search

Logging

Sergei Ostapov

Studio Pro records logs in multiple places depending on whether the workflow is saved to a .neek file or not.

  • Unsaved .neek files save their logs in C:\Users\{username}\electroNeek\logs\
  • Saved .neek files save their logs in {neek_file_location}\logs\{neek_file_name}\
    • Example: if your .neek file is located at C:\Users\Administrator\Desktop\Test\Test.neek your log folders would be at C:\Users\Administrator\Desktop\Test\logs\Test

The logs for a workflow are accessible through Studio’s menu. It will open the correct location both if the workflow is saved or not.

1en.png

Types of Logs

Studio Pro maintains logs for the console (within Studio Pro), exceptions from running Studio Pro, and autologs (when enabled) of your system’s information, Studio Pro configuration, and every step of the bot run.

 

Autologs

The autolog file is the main and the most important resource of information that you can receive and send us in order to solve a certain issue. 

It contains all the information in regard to your machine specifications, Studio Pro’s and its components’ versions and also every step of the workflow. Thus, it is the most detailed log-file created automatically. 

There is a certain structure of the file:

  1. Environment information (OS version, components versions, etc.)
  2. Information describing every step of the bot. Start and end of the bot’s work are also recorded. 

The information is displayed as: “Time of log-message - JSON”, for example:

16:26:46.328 {"programs":[{"program":"InternetExplorer","version":"11.789.19041.0"},

{"program":"Chrome","version":"91.0.4472.124"},

{"program":"1C"},{"program":"ElectroNeek Studio","version":"5.6.11.0"},

{"program":"ElectroNeek Robot","version":"5.6.11.0"},

{"program":"msedgedriver.exe","version":"79.0.313.0"}],"windows":{"caption":" Windows 10 Pro","version":"10.0.19042","csd_version":0,"os_architecture":"64-bit"},

"cpu":{"name":"AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx","number_of_cores":4,"number_of_logical_processors":0,"number_of_logicalprocessors":8},

17:03:21.706 {"activity_name":"START","file":"C:\\Users\\owlyo\\Desktop\\Bot Text\\Text bot.neek
","script_id":"b8c90d98-e2a5-49c2-9ddd-28d77172bb59","memory_usage":117484,"version":{"launched_by":"5.6.11","created_in":"5.6.11","updated_in":"5.6.11"},"start_time_iso":"2021-06-29T12:03:21.692Z","activity_group":"General","end_time_iso":"2021-06-29T12:03:21.693Z","duration_ms":1,"status":"success","error_message":null,"output_result":null,"executed_branch":"next","parameters":[{"name":"version","value":"4.0.0"}

Studio Pro Autologs

In order to enable that type of logging, go to “Settings” → “Execution” and enable the “Automatically create logs for each run” option. 

2en.png

The autolog file will be saved in the same directory as the workflow. 

For example: 

C:\Users\Username\Desktop\Project 1\logs\Project 1\studio_autologs

 

Bot Runner Autologs

The same can be applied for the ElectroNeek Bot Runner app. Follow these steps to enable logging:

  • Right click on Bot Runner icon in the tray;
  • Go to the “Settings” menu;
  • Go to the “Execution” tab;
  • Check the “Automatically create logs for each run” box.

The autologs can be found in C:\Users\Username\ElectroNeek\logs\robot folder or simply by pressing on the “Open logs” button (right click on Bot Runner icon in the tray).

 

Console logs

All of the information that is displayed in the Studio Pro console while working with the product and while the algorithm is running is logged in a separate file. This can be convenient in situations where detailed logging of each action is not required, while the console displays explanatory texts for the user (for example, values of key variables), which allows you to immediately see this in the console log file, instead of searching for this information in the long autologues.

 

Translated with www.DeepL.com/Translator (free version)

 

These logs are located at:

C:\Users\Username\electroNeek\logs\

OR

Under a log folder where the .neek file is saved. For example: if your .neek file is located at C:\Users\Administrator\Desktop\Test\Test.neek ,  your log folders would be at C:\Users\Administrator\Desktop\Test\logs\Test

The structure of console logs looks like this:

[DATE and TIME] : [MESSAGE TYPE]: MESSAGE

Here is an example:

[2021-06-28T10:00:12.199Z] : [info]: ---------------------------------------------

[2021-06-28T10:00:26.728Z] : [success]: Bot started.

[2021-06-28T10:00:26.730Z] : [info]: Robot start

[2021-06-28T10:00:30.160Z] : [success]: Bot finished successfully, total execution time: 3s 427ms.

 

Exception logs

Exception logs log the exceptions encountered by Studio when running. These logs are typically referred to the environment issues or issues with Studio that do not necessarily coincide with the running of a workflow.

 

Like the other logs, Exception logs are only located in the ElectroNeek folder located at C:\Users\Username\ElectroNeek\logs\studio_exceptions.

OR

Under a log folder where the .neek file is saved. For example: if your .neek file is located at C:\Users\Administrator\Desktop\Test\Test.neek ,  your log folders would be at C:\Users\Administrator\Desktop\Test\logs\Test

The structure of the exception log file displays the name of an error and the place where it occurred.

For example:

Unhandled Rejection at Promise

      getaddrinfo ENOTFOUND account.electroneek.co

Error: getaddrinfo ENOTFOUND account.electroneek.com

    at PortalBackendApi.transformError (C:\Program Files\ElectroNeek\Robot\resources\app.asar\dist\main.js:1:701496)

    at C:\Program Files\ElectroNeek\Robot\resources\app.asar\dist\main.js:1:701043

    at runMicrotasks (<anonymous>)

    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Related articles