@Since 7.0.0.3
Scheduled Event Messages are created when the next execution time of a Scheduled Event Function is reached. Messages will be saved for a period of 7 days after creation. This provides a way to track all the functions that have executed and debug as needed. Messages can be viewed by navigating to Administration → Scheduled Events and you will arrive at the Scheduled Event Messages screen.
Viewing Messages
The table shows all function executions within the last week. Messages are purged automatically after 7 days.
Field | Description |
|---|---|
Status | The status of the message. Can be SUCCESS, PENDING, or FAILED |
Function | The name of the function that was executed |
Message | A message containing more detail on the execution. This message can be set in a function’s script by using the LOG.setMessage function. If any errors occur during execution, the message will be overwritten |
Executed On | Date and time of function execution and message creation |
Resubmitted By *hidden | User who resubmitted the message |
Viewing Message Details
Click on any Scheduled Event Message row in the table to view more details about the function execution. A popup will open displaying log messages printed during the execution of the function’s groovy script. You can also re-submit a function execution from here with the Resubmit button. This is only meant to be used for debugging purposes. There is a global permission defined on groups to control who is allowed to resubmit event messages.
Log Messages
Logs are printed by using the LOG methods in the function groovy scripts. By default, the logging level will be based on the global FlexDeploy logging level. This can be modified specifically for event logs by setting the logging level for flexagon.fd.services.groovy.functions.LogFunctions in Administration → Admin Operations.
Some internal logs are printed automatically during execution. These logs will be at FINEST level.
