Create a scheduled change for a segment
Schedule semantic patch instructions to be applied to a segment at a future time.
Each instruction uses the same format as an instruction in a semantic patch request to update a segment. Send between 1 and 100 instructions. LaunchDarkly rejects the request with a 400 if an instruction has an unknown kind or is malformed.
The caller must be allowed to update scheduled changes on the segment, and must also be allowed to make each instruction’s change directly. If the segment requires approvals for an instruction, the caller must also be allowed to bypass them. Otherwise, request the change through an approval request instead. To learn more about semantic patches, read Updates.
Authorizations
Body
Response
Scheduled change created
The location and content type of related resources
Where the scheduled change is in its lifecycle. pending means the execution date is still in the future; inFlight means the change is being applied; failed means the change could not be applied on its execution date. More values may be added, so treat an unrecognized value as a change that has not been applied yet.
pending, inFlight, failed The ID of this scheduled change
The segment semantic patch instructions to apply on the execution date
The ID of the member who scheduled the change
The ID of the service token that scheduled the change
The comment describing the scheduled change