...
When an Event audit fails to be processed it results in the event being moved to this Audit section. The events here will not be automatically processed
...
Audit Functions
For each Event there is a range of functions that can assist with diagnosing issues. These functions are:
...
View Report
For each event there is a Report which will display additional information about the processing of the event. This will display the reason why the event failed to processed.
...
This will display a report similar to the following. The report will show any relevant information about the event and if there was any issues.
...
Run
This will process the event allowing to test whether a change has fixed any issues that have been shown.
Create Preview Context
This will create a Preview Context which is data that will assist in the creation of the templates.
Export
This will export the event data that was received from Jira as a json file. Event data is used to render the notifications with the correct information from the issue. This information can assist with PPL Support tickets.
View Event Data
This will display the event data using a json format. This allows you to view the field values that was set on the issue at that time.
Delete
This will remove the event from audit list.
Common Reasons for a Failed Event
Message size exceeds the mail server limit
Code Block |
---|
Error: Message size exceeds the configured message size restrictions of this mailbox. Please consult your (Mail Server) administrator. |
This error occurs when the outbound message exceeds the message size limit of your Mail Server. When this occurs it means that JEMHC is unable to send that message.
One way to prevent this from occurring is to set a total attachment size limit within the Notification mapping configuration. As this limit will remove all attachments from the notification email when the total size of attachments exceed this limit. As result the notification will still be sent but will not contain the attachments.
...
Unable to render event data. Webhook event data for events older than one hour are purged.
This error message occurs when the Webhook data for that event was removed. This occurs when the event did not process within an hour of when the event was triggered.
Report output
...