Dates and timing

Measure response and elapsed time

Measures elapsed or weekday business time and evaluates an SLA.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Distinguishes incomplete, invalid, reversed, measured, and SLA-breached intervals.

What to customize

Set unit, businessDays, weekdays, and optional slaHours.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "2026-01-05T09:00:00Z",
    "field2": "2026-01-05T13:00:00Z"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "4",
    "output2": "within_sla",
    "output3": "unit=hours;businessDays=false;calendar=UTC"
  }
}

Returned fields

output1: numeric duration
output2: SLA status
output3: unit and calendar mode

What changes when it runs

Reads two timestamps and performs local calculation.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe