Data pipeline usage

Workato measures data pipeline usage in Rows. Rows count the number of rows extracted from the source across all successful objects in each sync.

How rows are counted

The following diagram illustrates where usage is measured in a data pipeline. Rows are counted at extraction from the source, across all objects that sync successfully. Transformation and load steps don't add to the count.

Data pipeline calculation rules

Data pipeline usage calculations follow the general usage calculation rules, where rows from successful objects count toward usage and rows from failed objects are excluded.

Workato uses the following additional rules to calculate Rows:

  • Each row extracted from a successful object counts as 1 Row.
  • Rows from objects that fail to sync don't count toward usage. Failed objects are retried on later syncs. Once an object syncs successfully, its rows count then.
  • Transformation and load steps within a pipeline don't contribute to Rows.
  • Failed or canceled syncs count only the rows from objects that completed successfully before the failure or cancellation.
  • ETL or ELT performed in a workflow recipe is measured as workflow recipe usage, not as data pipeline usage.

Data pipeline usage examples

The following examples demonstrate how Workato calculates data pipeline usage.

Example: Successful sync

The following table demonstrates how usage is counted when all synced objects complete successfully:

ObjectSync statusRows extractedCounted
CustomersSuccess100100
OrdersSuccess250250
ProductsSuccess5050
Total Rows400

Each row extracted from a successful object counts as 1 Row.

Example: Sync with partial object failure

The following table demonstrates how usage is counted when a portion of the synced objects fail:

ObjectSync statusRows extractedCounted
CustomersSuccess100100
OrdersSuccess250250
ProductsFailed500
Total Rows350

Only rows extracted from successful objects count toward usage.

Last updated: