Docs
  • Solver
  • Models
    • Field Service Routing
    • Employee Shift Scheduling
    • Pick-up and Delivery Routing
  • Platform
Try models
  • Field Service Routing
  • User guide
  • Output datasets
  • Metadata

Field Service Routing

    • Introduction
    • Getting started: Hello world
    • User guide
      • Terminology
      • Use case guide
      • Planning AI concepts
      • Integration
      • Constraints
      • Understanding the API
      • Demo datasets
      • Input datasets
        • Model configuration
        • Model input
        • Planning window
        • Time zones and daylight-saving time (DST)
      • Routing with Timefold’s maps service
      • Input validation
      • Model response
      • Output datasets
        • Metadata
        • Model output
        • Input metrics
        • Key performance indicators (KPIs)
      • Key performance indicators (KPIs)
      • Metrics and optimization goals
    • Vehicle resource constraints
      • Shift hours and overtime
      • Lunch breaks and personal appointments
      • Fairness
      • Route optimization
      • Technician costs
      • Technician ratings
    • Visit service constraints
      • Time windows and opening hours
      • Skills
      • Visit dependencies
      • Multi-vehicle visits
      • Movable visits and multi-day schedules
      • Priority visits and optional visits
      • Visit service level agreement (SLA)
      • Visit requirements, area affinity, and tags
        • Visit requirements
        • Technician coverage area
        • Tags
    • Recommendations
      • Visit time window recommendations
      • Visit group time window recommendations
    • Real-time planning
      • Real-time planning: extended visit
      • Real-time planning: reassignment
      • Real-time planning: emergency visit
      • Real-time planning: no show
      • Real-time planning: technician ill
      • Real-time planning: pinning visits
    • Real-time planning with patches
      • Real-time planning: extended visit (using patches)
      • Real-time planning: reassignment (using patches)
      • Real-time planning: emergency visit (using patches)
      • Real-time planning: no show (using patches)
      • Real-time planning: technician ill (using patches)
      • Real-time planning: pinning visits (using patches)
    • Scenarios
      • Long-running visits
      • Configuring labor law compliance
    • Changelog
    • Upgrade to the latest version
    • Feature requests

Metadata

The metadata object includes information about the metadata for the dataset:

{
  "metadata": {
    "id": "ID",
    "parentId": "ID",
    "originId": "ID",
    "name": "dataset name",
    "submitDateTime": "2026-03-10T12:15:50-04:00",
    "startDateTime": "2026-03-10T12:15:50-04:00",
    "activeDateTime": "2026-03-10T12:15:50-04:00",
    "completeDateTime": "2026-03-10T12:15:50-04:00",
    "shutdownDateTime": "2026-03-10T12:15:50-04:00",
    "solverStatus": "DATASET_CREATED",
    "score": "0hard/0medium/100000soft",
    "tags": [
      "Control"
    ],
    "validationResult": {
      "summary": "OK",
      "errors": [
        "Error message"
      ],
      "warnings": [
        "Warning message"
      ]
    },
    "failureMessage": "string"
  }
}
  • id is the ID assigned to the dataset.

  • parentId identifies the dataset this dataset was derived from if the patch operation was used to create a new revision of the dataset.

  • originID identifies the original dataset this dataset was derived from if multiple patch operation were used to create new revisions of the dataset.

  • name is the name that was provided with the input dataset. If no name was provided, one will be automatically generated.

  • submitDateTime is when the dataset was submitted.

  • startDateTime is when the dataset started solving.

  • activeDateTime shows when the solve-phase of the run started.

  • completeDateTime shows when the solve-phase of the run stopped.

  • shutdownDateTime shows when the solver shut down.

  • solverStatus shows the status of the dataset. See dataset lifecycle for more details.

  • score is the hard, medium, and soft scores of the dataset. See constraints for more information about constraint scores.

  • tags contains any tags that were included with the input dataset.

  • validationResult will return VALIDATION_NOT_SUPPORTED, OK, WARNINGS, ERRORS.

  • errors contains the list of errors that occurred during validation.

  • warning contains a list of warnings for the dataset, if any occur.

  • failureMessage describing the reason the run failed if the solverStatus is SOLVING_FAILED.

Next

  • See the full API spec or try the online API.

  • Learn more about field service routing from our YouTube playlist.

  • Learn about Model output object included in output datasets.

  • © 2026 Timefold BV
  • Timefold.ai
  • Documentation
  • Changelog
  • Send feedback
  • Privacy
  • Legal
    • Light mode
    • Dark mode
    • System default