---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# MID Server support

# MID Server support for Data Stream actions {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Get data through a ServiceNow® MID Server when running a Data Stream action.

When selected, the MID Server retrieves the data and sends each page to the
instance as an attachment to process.  
Important:  
When running the Data Stream action within flow, the actions in the For Each block always run on the instance.

These steps can run on either the MID Server or the instance:  
* Action Preprocessing Script
* Request Script step
* REST or SOAP step
{#dsa-on-mid__ul_pgy_scd_ljb}  
Note:  
Avoid shifting the execution environment between the instance and the MID Server multiple times. For example, you might configure the Request Script step to run on the MID Server, but the REST step to run on the instance. In this case, the system shifts environments between the instance and MID Server for every page of data, which may degrade performance.

To learn more about running a step on a MID Server, see [Integration steps](https://www.servicenow.com/docs/Nd5RPfllS8HtNkr12C9jJQ "Enable custom actions to integrate with external systems by activating Integration Hub, which adds integration steps to the Workflow Studio interface.").

## Size limits {#dsa-on-mid__section_srh_kgy_ljb}

If your system encounters a timeout or size limit issue, try making one of these
adjustments:  

Increase the REST transaction quota rule

:   If the connection between the instance and the MID Server slows down, you
    may encounter a timeout while waiting for a response from the REST step. Increase the
    default timeout by updating the REST Attachment API request timeout
    transaction quota rule.

    * Default: 60 seconds
    * Maximum: 300 seconds
    {#dsa-on-mid__ul_cbj_hpy_ljb}

Increase the instance timeout

:   By default, the instance waits for 600 seconds to retrieve a single page of data from a MID Server. If you encounter a timeout when running a Data Stream action through a MID Server, change this default by increasing the datastream_alternative_env_fetch_page_timeout_seconds system property.

    * Default: 600 seconds
    * Maximum: 7200 seconds
    {#dsa-on-mid__ul_gcj_r4y_ljb}

Increase attachment size
:   The MID Server sends each page of data to the instance as an attachment. If
    a page of data is large, it may exceed the allowed attachment size. Increase the allowed size
    by updating the com.glide.attachment.max_size system property.  
    * Default: 1024 MB
    * Maximum: None
    {#dsa-on-mid__ul_tq5_cty_ljb}

## JDBC operations and MID Server timeouts {#dsa-on-mid__section_gct_cym_mjc}

For JDBC operations, execute the Data Stream Action asynchronously and poll the Attachments \[sys_attachment\] table for results.

The MID Server processes the SQL statement, while the instance/main thread waits for context payloads to be inserted into the attachment table to query the next record.

You can adjust timeout values for JDBC operations with the following properties.  

com.snc.process_flow.datastream.payload.timeout.seconds
:   The amount of time the instance waits for the payload to be available from the JDBC execution in the MID Server. A bounded property with a minimum value of 0 seconds and a maximum value of 7200 seconds. The default
    time is 600 seconds.

com.snc.process_flow.datastream.async_child.timeout.seconds
:   The amount of time allocated for the execution of a child plan in the MID Server.A bounded property with a minimum value of 0 seconds and a maximum value of 7200 seconds. The default time is 60 seconds.