relays, objects, arrays [netlify-build]

Author: stayseesong

src/connections/reverse-etl/index.md

@@ -134,6 +134,8 @@ To check the status of your extractions:
     * The load results - how many successful records were synced as well as how many records were updated, deleted, or are new.
 5. If your sync failed, click the failed reason to get more details on the error and view sample payloads to help troubleshoot the issue.
 
+#### Replays
+You can choose to replay syncs. To replay a specific sync, contact [[email protected]](mailto:[email protected]). Keep in mind that triggering a replay resyncs all records for a given sync.
 
 ### Edit your model
 
@@ -167,44 +169,6 @@ The Segment Connections destination enables you to mold data extracted from your
 > warning ""
 >  The Segment Connections destination sends data to Segment’s Tracking API, which has cost implications. New users count as new MTUs and each call counts as an API call. For information on how Segment calculates MTUs and API calls, please see [MTUs, Throughput and Billing](/docs/guides/usage-and-billing/mtus-and-throughput/).
 
-## Limits
-To provide consistent performance and reliability at scale, Segment enforces default use and rate limits for Reverse ETL.
-
-### Usage limits
-Reverse ETL usage limits are measured based on the number of records processed to each destination – this includes both successful and failed records. For example, if you processed 50k records to Braze and 50k records to Mixpanel, then your total Reverse ETL usage is 100k records.
-
-Processed records represents the number of records Segment attempts to send to each destination. Keep in mind that not all processed records are successfully delivered, for example, such as when the destination experiences an issue.
-
-Your plan determines how many Reverse ETL records you can process in one monthly billing cycle. When your limit is reached before the end of your billing period, your syncs will pause and then resume on your next billing cycle. To see how many records you’ve processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab.
-
-Plan | Number of Reverse ETL records you can process to destinations per month | How to increase your number of Reverse ETL records
----- | --------------------------------------------------------------------------- | ---------------------------------------------------
-Free | 500K | Upgrade to the Teams plan in the Segment app by navigating to **Settings > Usage & billing**.
-Teams | 1 million | Contact your sales representative to upgrade your plan to Business.
-Business | 50 x the number of [MTUs](/docs/guides/usage-and-billing/mtus-and-throughput/#what-is-an-mtu) <br>or .25 x the number of monthly API calls | Contact your sales rep to upgrade your plan.
-
-If you have a non-standard or high volume usage plan, you may have unique Reverse ETL limits or custom pricing.
-
-### Configuration limits
-
-Name | Details | Limit
---------- | ------- | ------
-Model query length | The maximum length for the model SQL query. | 131,072 characters
-Model identifier column name length | The maximum length for the ID column name. | 191 characters
-Model timestamp column name length | The maximum length for the timestamp column name. | 191 characters
-Sync frequency | The shortest possible duration Segment allows between syncs. | 15 minutes
-
-### Extract limits
-The extract phase is the time spent connecting to your database, executing the model query, updating internal state tables and staging the extracted records for loading.
-
-Name | Details | Limit
------ | ------- | ------
-Record count | The maximum number of records a single sync will process. Note: This is the number of records extracted from the warehouse not the limit for the number of records loaded to the destination (for example, new/update/deleted). | 30 million records
-Column count | The maximum number of columns a single sync will process. | 512 columns
-Column name length | The maximum length of a record column. | 128 characters
-Record JSON size | The maximum size for a record when converted to JSON (some of this limit is used by Segment). | 512 KiB
-Column JSON size | The maximum size of any single column value. | 128 KiB
-
 ## Supported Object and Arrays 
 
 When you set up destination actions in Reverse ETL, depending on the destination, some mapping fields may require data to be in the form of an object or array. 
@@ -268,4 +232,42 @@ Customize array | This enables you to select the specific nested properties to s
 > success ""
 > Certain array mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your array don't match the destination properties, the data won't send. Segment recommends you to use the **Customize array** option to ensure your mapping is successful.
 
-Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property. 
+Objects in an array don't need to have the same properties. If a user selects a missing property in the input object for a mapping field, the output object will miss the property. 
+
+## Limits
+To provide consistent performance and reliability at scale, Segment enforces default use and rate limits for Reverse ETL.
+
+### Usage limits
+Reverse ETL usage limits are measured based on the number of records processed to each destination – this includes both successful and failed records. For example, if you processed 50k records to Braze and 50k records to Mixpanel, then your total Reverse ETL usage is 100k records.
+
+Processed records represents the number of records Segment attempts to send to each destination. Keep in mind that not all processed records are successfully delivered, for example, such as when the destination experiences an issue.
+
+Your plan determines how many Reverse ETL records you can process in one monthly billing cycle. When your limit is reached before the end of your billing period, your syncs will pause and then resume on your next billing cycle. To see how many records you’ve processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab.
+
+Plan | Number of Reverse ETL records you can process to destinations per month | How to increase your number of Reverse ETL records
+---- | --------------------------------------------------------------------------- | ---------------------------------------------------
+Free | 500K | Upgrade to the Teams plan in the Segment app by navigating to **Settings > Usage & billing**.
+Teams | 1 million | Contact your sales representative to upgrade your plan to Business.
+Business | 50 x the number of [MTUs](/docs/guides/usage-and-billing/mtus-and-throughput/#what-is-an-mtu) <br>or .25 x the number of monthly API calls | Contact your sales rep to upgrade your plan.
+
+If you have a non-standard or high volume usage plan, you may have unique Reverse ETL limits or custom pricing.
+
+### Configuration limits
+
+Name | Details | Limit
+--------- | ------- | ------
+Model query length | The maximum length for the model SQL query. | 131,072 characters
+Model identifier column name length | The maximum length for the ID column name. | 191 characters
+Model timestamp column name length | The maximum length for the timestamp column name. | 191 characters
+Sync frequency | The shortest possible duration Segment allows between syncs. | 15 minutes
+
+### Extract limits
+The extract phase is the time spent connecting to your database, executing the model query, updating internal state tables and staging the extracted records for loading.
+
+Name | Details | Limit
+----- | ------- | ------
+Record count | The maximum number of records a single sync will process. Note: This is the number of records extracted from the warehouse not the limit for the number of records loaded to the destination (for example, new/update/deleted). | 30 million records
+Column count | The maximum number of columns a single sync will process. | 512 columns
+Column name length | The maximum length of a record column. | 128 characters
+Record JSON size | The maximum size for a record when converted to JSON (some of this limit is used by Segment). | 512 KiB
+Column JSON size | The maximum size of any single column value. | 128 KiB