Dataddo | Status

Dataddo | Status

Back
Jan 29, 2025 6:40 AM UTC Resolved after 2h 44m

Restarting stuck actions

Impacted:
Extractor
Dataddo Core

Updates

  • Jan 29, 2025 9:24 AM UTC

    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.

    Resolved
  • Jan 29, 2025 7:48 AM UTC (1 hour and 36 minutes earlier)

    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.

    Identified
  • Jan 29, 2025 7:11 AM UTC (36 minutes earlier)

    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.

    Identified
  • Jan 29, 2025 6:40 AM UTC (31 minutes earlier)

    Jobs are processed longer than usual

    Investigating