sensorRequestReSubmitForService mutation

Re-runs every sensor request that discovered the specified Service, as sensorRequestReSubmit does for one request. Unlike that mutation, this one respects the organization's sensorScopes, so it returns an empty list when the scopes allow none of the sensors, when the service has no originating requests, or when the sensor no longer accepts requests. Requests are reset one at a time, so an error partway through leaves the earlier ones reset.

Response

Returns a SensorRequestSubmitForServicePayload!

Arguments

Name	Description
`id` - `ID!`	The graph object id of the Service.

Example

Query

mutation sensorRequestReSubmitForService($id: ID!) {
  sensorRequestReSubmitForService(id: $id) {
    sensorRequests {
      id
      device {
        ...DeviceFragment
      }
      sensor {
        ...SensorFragment
      }
      zone
      ip {
        ...IpAddressFragment
      }
      protocol
      port
      args
      created
      state {
        ...SensorRequestStateFragment
      }
      runIds
      runs {
        ...SensorRequestRunFragment
      }
    }
  }
}

Variables

{"id": "4"}

Response

{
  "data": {
    "sensorRequestReSubmitForService": {
      "sensorRequests": [SensorRequest]
    }
  }
}