Hey Team Sharing the error from the from the #ingestion channel thread as @steep-midnight-37232 also reported it for 0.8.44. Getting similar error for multiple integrations.

~~~~ Execution Summary ~~~~

RUN_INGEST - {'errors': [],
 'exec_id': '8cc88fff-6200-465e-9d09-703160d417fc',
 'infos': ['2022-09-12 13:20:11.799891 [exec_id=8cc88fff-6200-465e-9d09-703160d417fc] INFO: Starting execution for task with name=RUN_INGEST',
           '2022-09-12 13:20:11.801144 [exec_id=8cc88fff-6200-465e-9d09-703160d417fc] INFO: Caught exception EXECUTING '
           'task_id=8cc88fff-6200-465e-9d09-703160d417fc, name=RUN_INGEST, stacktrace=Traceback (most recent call last):\n'
           '  File "/usr/local/lib/python3.9/site-packages/acryl/executor/execution/default_executor.py", line 121, in execute_task\n'
           '    self.event_loop.run_until_complete(task_future)\n'
           '  File "/usr/local/lib/python3.9/site-packages/nest_asyncio.py", line 89, in run_until_complete\n'
           '    return f.result()\n'
           '  File "/usr/local/lib/python3.9/asyncio/futures.py", line 201, in result\n'
           '    raise self._exception\n'
           '  File "/usr/local/lib/python3.9/asyncio/tasks.py", line 256, in __step\n'
           '    result = coro.send(None)\n'
           '  File "/usr/local/lib/python3.9/site-packages/acryl/executor/execution/sub_process_ingestion_task.py", line 71, in execute\n'
           '    validated_args = SubProcessIngestionTaskArgs.parse_obj(args)\n'
           '  File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj\n'
           '  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__\n'
           'pydantic.error_wrappers.ValidationError: 1 validation error for SubProcessIngestionTaskArgs\n'
           'debug_mode\n'
           '  extra fields not permitted (type=value_error.extra)\n']}
Execution finished with errors.

I'm running DataHub in GCP Kubernetes Engine and have also tried uninstalling and reinstalling with helm.

Hi, checkout this thread: https://datahubspace.slack.com/archives/C029A3M079U/p1662416809883409 May be the same problem.

Thanks @fast-oyster-93603, updating datahub actions from 0.0.4 to 0.0.6 resovled this issue.