@@ -56,7 +56,9 @@ final class StartExecutionInput extends Input
56
56
* - brackets `< > { } [ ]`
57
57
* - wildcard characters `? *`
58
58
* - special characters `" # % \ ^ | ~ ` $ & , ; : /`
59
- * - control characters (`U+0000-001F`, `U+007F-009F`)
59
+ * - control characters (`U+0000-001F`, `U+007F-009F`, `U+FFFE-FFFF`)
60
+ * - surrogates (`U+D800-DFFF`)
61
+ * - invalid characters (` U+10FFFF`)
60
62
*
61
63
* To enable logging with CloudWatch Logs, the name should only contain 0-9, A-Z, a-z, - and _.
62
64
*
@@ -69,9 +71,9 @@ final class StartExecutionInput extends Input
69
71
/**
70
72
* The string that contains the JSON input data for the execution, for example:
71
73
*
72
- * `"input": " {\"first_name\" : \"test \"}"`
74
+ * `"{\"first_name\" : \"Tim \"}"`
73
75
*
74
- * > If you don't include any JSON input data, you still must include the two braces, for example: `"input": " {}"`
76
+ * > If you don't include any JSON input data, you still must include the two braces, for example: `"{}"`
75
77
*
76
78
* Length constraints apply to the payload size, and are expressed as bytes in UTF-8 encoding.
77
79
*
@@ -82,6 +84,11 @@ final class StartExecutionInput extends Input
82
84
/**
83
85
* Passes the X-Ray trace header. The trace header can also be passed in the request payload.
84
86
*
87
+ * > For X-Ray traces, all Amazon Web Services services use the `X-Amzn-Trace-Id` header from the HTTP request. Using
88
+ * > the header is the preferred mechanism to identify a trace. `StartExecution` and `StartSyncExecution` API operations
89
+ * > can also use `traceHeader` from the body of the request payload. If **both** sources are provided, Step Functions
90
+ * > will use the **header value** (preferred) over the value in the request body.
91
+ *
85
92
* @var string|null
86
93
*/
87
94
private $ traceHeader ;
0 commit comments