Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Misleading Execution Log

Misleading Execution Log 3 months 1 week ago #19231

AETLP x32 v6.3.4.9

Hi, This not a big issue but I do find myself getting mislead from time to time. But in this package we process a list of files and then at the end of the list we do some cleanup.

In the example below you can see that the Loop comes to and end and the Cleanup Action runs. On first review of the log it 'appears' that an error occurred due to the 'red' colour.

Whilst the end of the list file was found and technically is probably being caught as an error with in AETL I find it misleading to have the 'red' highlighted row when in fact coming to the end of the list file is to be expected and a normal exit point.

Even the textual LOG file does not show any indication of an 'error'

I realise that we could put conditional logic around to avoid this - but it seems to me to be a waste of effort and that AETL could possibly be a little more precise in this scenario - when no actual error has occurred other than coming to the end of the list file

cheers


Attachments:

Please Log in or Create an account to join the conversation.

Misleading Execution Log 2 months 3 weeks ago #19279

  • admin
  • admin's Avatar
  • Offline
  • Moderator
  • Moderator
  • Deeds not Words
  • Posts: 7618
  • Karma: 33
  • Thank you received: 419
Hi Bruce

That was corrected in the latest release

Full list of changes

+ Added: Clear log Action
+ Improved: Loop Action Logging
+ Improved: Set Variable Action
+ Fixed: Project clone issues
+ Improved: Salesforce connection uses TLS 1.2 now
Mike

Please Log in or Create an account to join the conversation.

  • Page:
  • 1

We have 238 guests and no members online