RequestEntityTooLargeException exception thrown by start_execution_manager

[asjohnston-asf]

[ERROR]    2024-05-02T19:43:05.951Z    45a949f4-9de2-417d-b272-c92c1bc0e7ed    Unhandled exception
Traceback (most recent call last):
  File "/var/task/lambda_logging/__init__.py", line 18, in wrapper
    lambda_handler(event, context)
  File "/var/task/start_execution_manager.py", line 35, in lambda_handler
    response = invoke_worker(worker_function_arn, jobs)
  File "/var/task/start_execution_manager.py", line 16, in invoke_worker
    return LAMBDA_CLIENT.invoke(
  File "/var/task/botocore/client.py", line 565, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/var/task/botocore/client.py", line 1021, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (RequestEntityTooLargeException) when calling the Invoke operation: 264496 byte payload is too large for the Event invocation type (limit 262144 bytes)

The start_execution_manager lamba invokes the start_execution_worker lambda with a list of job records. We've made a number of changes over the past months that increase the size of individual job records that can push the list over the 262144 bytes payload limit in certain circumstances:

• 6.0.0 added a credit_cost field for each job
• 6.1.0 began populating default values for all job parameters, rather than just those provided by the user
• 7.1.0 added goldstein_filter_power, output_resolution, unfiltered_coherence, and dense_offsets parameters to INSAR_ISCE jobs

See #1676 and #1689 for more historical context.