---
title: "Health Checks for Input and Output Connections"
slug: "health-checks-for-input-and-output-connections"
updated: 2026-05-06T10:42:51Z
published: 2026-05-06T19:13:31Z
canonical: "help.hyperscience.ai/health-checks-for-input-and-output-connections"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Health Checks for Input and Output Connections

> [!WARNING]
> **Creating connections**
> 
> Depending on your license package and pricing plan, you may not be able to create all of the connects described in this article.
> 
> To learn which features are available to your organization and how to add more, contact your Hyperscience representative.

The system conducts periodic health checks on the components of the instance, including various aspects of any input or output connections configured in deployed flows.

By default, these health checks are performed every 30 seconds, but you can change this interval by editing the value of the `HEALTH_CHECK_INTERVAL` ".env" file variable. The interval applies to all components, so it is not possible to set one interval for connections and another for the rest of the system. To learn more about this value, see [Health Check Interval](https://help.hyperscience.com/deployment/docs/health-check-interval).

## Input connections

The health checks performed for input connections are described in the table below.

| Connection | Health checks performed | Notes |
| --- | --- | --- |
| **Message Queue Listener** | - Credentials are working. - Queue exists. | It doesn’t check that it is possible to receive a message from the queue (i.e., that read permissions are set correctly). |
| [v42.3 and later] **SQS Listener** | - Credentials are working. - Queue exists. | It doesn’t check that it is possible to receive a message from the queue (i.e., that read permissions are set correctly). |
| **Email Listener** | - Generic (IMAP) - Credentials are correct, and it is possible to login to the IMAP server. - Folder specified in **Folder To Scan For Emails** exists. - If set, folder specified in **Post Process Archive Folder** (where the email is moved after processing) exists. - Microsoft 365 Outlook - Credentials are correct. - Username exists. - Folder specified in **Folder To Scan For Emails** exists. - If set, folder specified in **Post Process Archive Folder** (where the email is moved after processing) exists. | It doesn’t read any email or check for read-email permissions. |
| **Folder Listener** | - Folder specified in **Folder To Scan For Submissions** exists. - Read and write permissions are granted on the folder being scanned for submissions. - Configuration is valid (e.g., intervals set in **Poll Interval** and **Warm-up Interval** are not negative). |  |
| **Kafka Listener** | - Bootstrap server is reachable. - Topics exist. |  |
| **Universal Folder Listener** | - Folder specified in **Folder To Scan For Submissions** exists. - Read and write permissions are granted on the folder being scanned for submissions. - Configuration is valid (e.g., intervals set in **Poll Interval (In Seconds)** and **Warm-up Interval** **(In Seconds)** are not negative). |  |
| **S3 Listener** | - Credentials are correct. - Permissions on the bucket are correct (`PUT`, `LIST`, `GET`, `DELETE`) for both the input bucket (specified in **S3 Source URI**) and the destination bucket (specified in **S3 Archive URI**). |  |
| **Salesforce Listener** | - Credentials are correct and authentication is possible. - Salesforce streaming channel with the name provided in **Channel Name** exists. - There is a record for the channel name specified in the `Hyperscience__Channel_Object_Link__c` object. |  |
| **Box Listener** | - Credentials are correct and authentication is possible. - Folder specified in **Folder To Scan For Submissions** exists, and permissions are sufficient. - Folder specified in **Folder to Move Completed Files** exists, and permissions are sufficient. |  |

## Output connections

The table below contains details on the health checks performed for output connections.

| Connection | Health checks performed | Notes |
| --- | --- | --- |
| **Message Queue Notifier** | - Credentials are working. - Queue exists. | It doesn’t check that it is possible to send a message to the queue, (i.e., that publish permissions are set correctly). |
| [v42.3 and later] **SQS Notifier** | - Credentials are working. - Queue exists. | It doesn’t check that it is possible to send a message to the queue, (i.e., that publish permissions are set correctly). |
| **HTTP Notifier** | - It is possible to send a `GET` request to the endpoint URL (i.e., the endpoint is reachable). | It doesn’t check if the provided credentials are correct. |
| **UiPath Notifier** | - It is possible to obtain an authentication token with the provided credentials. - If the `UIPATH_TEST_QUEUE_EXISTENCE` “.env” file variable is set, checks if the queue specified as that variable’s value exists. |  |
| **Kafka Notifier** | - Bootstrap server is reachable. - Topic exists. |  |
| **S3 Notifier** | - Credentials are correct. - Permissions on the bucket specified in **S3 URI** are correct (`PUT`). |  |
| **Salesforce Notifier** | - Authentication to Salesforce succeeds. - Salesforce object with the name specified in **Object API Name** exists. - Validation succeeds for the mapping specified in **Lookup Field Mapping** (i.e., the mapping exists). - Validation succeeds for the mappings listed in **Document Field Mappings** (i.e., the mappings exist). |  |
| **Box Notifier** | - Credentials are correct and authentication is possible. - Box template with the template name provided in the configuration exists. - Box metadata template with the metadata template name provided in the configuration exists. - Box template fields set in the configuration exist. |  |