Script execution and system log for LogRhythm

---
title: Script execution and system log for LogRhythm
description: If you are troubleshooting an alarm ingestion issue, you can override the default five-minute polling interval to view results immediately. In this scenario, call the script execution manually to execute polling. This execution is optional.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/script-execution-logrhythm.html
release: australia
product: Security Incident Response
classification: security-incident-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Troubleshooting the LogRhythm integration, LogRhythm Overview, Security Incident Response integrations, Security Incident Response, Enterprise security case management applications, Security Operations]
---

# Script execution and system log for LogRhythm

If you are troubleshooting an alarm ingestion issue, you can override the default five-minute polling interval to view results immediately. In this scenario, call the script execution manually to execute polling. This execution is optional.

## Before you begin

Role required: sn\_si.admin

## Procedure

1.  Navigate to **All** > **Scheduled job** > **Scheduled Jobs** and select the **Scheduled Jobs** module.

2.  Click the Process LogRhythm integrations job record.

3.  In the Scheduled Script Execution record that is displayed, click **Execute Now**.

    \[Omitted image "scheduledjob02\_\_job\_detail\_with\_execute\_now\_button.png"\] Alt text: Execute Now button highlighted.

    If you require more troubleshooting help, you can access the system log for the LogRhythm queries.

4.  For other general troubleshooting issues, follow these steps to access the system logs.

    1.  Navigate to **System log** > **All** and select **All**.

    2.  Set the filter \(`Go to`\) to **Source** and enter `sn_sec_logrhythm`.

    3.  Press **Enter**.

        Any messages generated by the integration are displayed in this table. The messages listed can provide insight into the running processes of the integration, and they may assist you with further troubleshooting.


**Parent Topic:**[Troubleshooting the LogRhythm integration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/troubleshooting-logrhythm-integration.md)