send_task_success
¶
send_task_success(
task_token: TaskToken,
output: SensitiveData,
*,
config_overrides: Optional[SFNClientConfig] = None,
) -> SendTaskSuccessOutput
Used by activity workers, Task states using the callback pattern, and optionally Task states using the job run pattern to report that the task identified by the taskToken completed successfully.
Parameters:
-
task_token(TaskToken) –The token that represents this task. Task tokens are generated by Step Functions when tasks are assigned to a worker, or in the context object when a workflow enters a task state. See GetActivityTaskOutput$taskToken.
-
output(SensitiveData) –The JSON output of the task. Length constraints apply to the payload size, and are expressed as bytes in UTF-8 encoding.
Raises:
-
InvalidOutput–The provided JSON output data is not valid.
-
InvalidToken–The provided token is not valid.
-
KmsAccessDeniedException–Either your KMS key policy or API caller does not have the required permissions.
-
KmsInvalidStateException–The KMS key is not in valid state, for example: Disabled or Deleted.
-
KmsThrottlingException–Received when KMS returns
ThrottlingExceptionfor a KMS call that Step Functions makes on behalf of the caller. -
TaskDoesNotExist–The activity does not exist.
-
TaskTimedOut–The task token has either expired or the task associated with the token has already been closed.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_sfn/_services/sfn.py
1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 | |