Log record created when a logged event is triggered
Elements
The rb.schedule.log.logDef struct has 10 elements:
Name
Type/Value
Range/Length
Description
ID
number
Optional. Unique ID of this schedule log record
eventID
number
Optional. The ID of the event to which this log applies. Note that the event record itself may no longer exist. This can't be changed once the log record is created.
actionID
number
Optional. The ID of the action that was triggered for this event. Note that the action record itself may no longer exist. This can't be changed once the log record is created.
created
date
Optional. Date/time at which this log entry was created
expected
date
Optional. Date/time at which the event/action that this log entry records should be been triggered
url
string
Optional. The URL that was called for this event. This will initially exclude trigger parameters (wbsched-id and wbsched-logid) which
will be included once the URL call has completed. Can't be changed by the application.
elapsed
number
Optional. The time taken to request the URL for this event. Will be null until the call is complete. Read-only.
httpCode
number
Optional. The HTTP response code returned from the remote server. This will be null until the call is complete. Read-only
responseBody
string
Optional. The HTTP body returned from the action URL if body logging is enabled. Read-only.
customData
MetaData
Optional.
custom data stored against this log entry. This information will have been stored through the template interface rb.schedule.log.modify call
usually by the page invoked by the trigger URL. Applications can use this to store debug information against the specific event.
