get_durable_execution_history
async
¶
get_durable_execution_history(
durable_execution_arn: DurableExecutionArn,
*,
config_overrides: Optional[AsyncLambdaClientConfig] = None,
include_execution_data: Optional[IncludeExecutionData] = None,
max_items: Optional[ItemCount] = None,
marker: Optional[String] = None,
reverse_order: Optional[ReverseOrder] = None,
) -> GetDurableExecutionHistoryResponse
Retrieves the execution history for a durable execution, showing all the steps, callbacks, and events that occurred during the execution. This provides a detailed audit trail of the execution's progress over time.
The history is available while the execution is running and for a retention period after it completes (1-90 days, default 30 days). You can control whether to include execution data such as step results and callback payloads.
Parameters:
-
durable_execution_arn(DurableExecutionArn) –The Amazon Resource Name (ARN) of the durable execution.
-
include_execution_data(Optional[IncludeExecutionData], default:None) –Specifies whether to include execution data such as step results and callback payloads in the history events. Set to
trueto include data, orfalseto exclude it for a more compact response. The default istrue. -
max_items(Optional[ItemCount], default:None) –The maximum number of history events to return per call. You can use
Markerto retrieve additional pages of results. The default is 100 and the maximum allowed is 1000. A value of 0 uses the default. -
marker(Optional[String], default:None) –If
NextMarkerwas returned from a previous request, use this value to retrieve the next page of results. Each pagination token expires after 24 hours. -
reverse_order(Optional[ReverseOrder], default:None) –When set to
true, returns the history events in reverse chronological order (newest first). By default, events are returned in chronological order (oldest first).
Raises:
-
InvalidParameterValueException–One of the parameters in the request is not valid.
-
KMSAccessDeniedException–Lambda couldn't decrypt the environment variables because KMS access was denied. Check the Lambda function's KMS permissions.
-
KMSDisabledException–Lambda couldn't decrypt the environment variables because the KMS key used is disabled. Check the Lambda function's KMS key settings.
-
KMSInvalidStateException–Lambda couldn't decrypt the environment variables because the state of the KMS key used is not valid for Decrypt. Check the function's KMS key settings.
-
KMSNotFoundException–Lambda couldn't decrypt the environment variables because the KMS key was not found. Check the function's KMS key settings.
-
ResourceNotFoundException–The resource specified in the request does not exist.
-
ServiceException–The Lambda service encountered an internal error.
-
TooManyRequestsException–The request throughput limit was exceeded. For more information, see Lambda quotas.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_lambda/_services/async__lambda.py
2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 | |