Updates a fielding run
PUT/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}
Update a specific fielding run of a target group. Fielding runs can only be updated for target groups in either scheduled, live or paused status. The operation will fail if the target group status is completed.
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 412
- 422
- 429
- 500
A successful updated fielding run response.
Response Headers
The traceparent header primarily carries essential trace context information, including the trace ID and parent span ID as defined by the W3C trace context specification. It's used to pinpoint the position of an incoming request within the trace graph, facilitating the tracking of distributed operations.
The tracestate header complements the traceparent header by providing additional contextual information, thereby allowing for the enrichment of tracing context and offering more fine-grained control.
The ETag header provides a unique identifier, that represents the current version state of a particular resource.
A request is not valid and can't be processed.
A request is unauthorized.
A requested is forbidden.
A requested resource isn't found.
Resource could not be modified due to wrong expected version
Response Headers
The traceparent header primarily carries essential trace context information, including the trace ID and parent span ID as defined by the W3C trace context specification. It's used to pinpoint the position of an incoming request within the trace graph, facilitating the tracking of distributed operations.
The tracestate header complements the traceparent header by providing additional contextual information, thereby allowing for the enrichment of tracing context and offering more fine-grained control.
A request failed due to invalid state of the entity
Rate limiting
Response Headers
The traceparent header primarily carries essential trace context information, including the trace ID and parent span ID as defined by the W3C trace context specification. It's used to pinpoint the position of an incoming request within the trace graph, facilitating the tracking of distributed operations.
The tracestate header complements the traceparent header by providing additional contextual information, thereby allowing for the enrichment of tracing context and offering more fine-grained control.
How long the user agent should wait before making a follow-up request.
A request failed due to an internal error.