Execution History

The execution history contains a detailed trace of the last 100 MLM executions. New entries will only be added if the execution log is enabled.

Each column can be clicked to sort by it and sort mode changed between ascending or descending by further clicks.

Origin

The origin describes how that MLM execution came to be. Three fields can identify any possible origin:

• Synchronous is a simple yes/no that describes whether the caller of the MLM waited for a result. Asynchronous executions are often the result of calls by evoke slot, for example extensions that work off an event queue.
• Source denotes the nature of the caller and is one of REST, PLUGIN, MLM or SYSTEM.
  • REST is MLMs called directly via frontend (e.g., debugging) or API
  • PLUGIN is MLMs called by plugins, mostly via events, for example a CDS Hooks MLM
  • MLM is MLMs called by other MLMs, via the CALL statement.
    • CALL EVENT is special since it goes through events, so MLMs called by it will have the source PLUGIN
  • SYSTEM is MLMs called by ArdenSuite itself for analysis reasons, like parsing an evoke slot. They are usually hidden.
• Method denotes the reason or purpose for the call. It is one of EVOKE, CALL, RUN, DEBUG or ANALYSE.
  • EVOKE is an MLM triggered by its evoke slot, usually with source PLUGIN
  • CALL is an MLM called by its name, version and institution, usually with source REST.
  • RUN is a temporary MLM only run by provided source code, usually also with source REST.
  • DEBUG is an MLM call coupled with a debug configuration, usually by the frontend and with source REST.
  • ANALYSE is an MLM call for various parsing reasons, exclusively used with source SYSTEM.

Details

Each row can be expanded or collapsed by clicking the little arrow to its left.

The detail contains a list of arguments provided to the MLM (left), a stack trace of other MLMs and plugins it called (middle), and a list of values it returned (right).