All affected actions (extractions and following flows) were restarted. In each affected extraction log, you find the execution with "failed to set timeout: deadline can't be prolonged" error.

The extractions/flows behavior is now as expected.

We ran command/script to restart all stuck extractions. Such action's last execution log result to be "broken" and the new execution would start immediately. If the extraction has following flow attached this will be triggered automatically once the extractions finishes with no error.

We have identified that extractions were executed according to their scheduled configurations. However, the extractor component failed to send results to the result queue.

This issue affected all extractions processed in the AWS environment, while extractions in the GCP environment remained unaffected.

We are now updating all affected actions to a “broken” status and will restart them to ensure the triggering of subsequent flows.

Jobs are processed longer than usual