Skip to content

try/except in orchestrator functions not being handled correctly #20

@cgillum

Description

@cgillum

There are two issues with try/except handling in orchestrator functions

  1. Only the first task in an except block actually runs
  2. The completed action in the except block always results in the original error being re-raised

The issue is that the internal state machine does not correctly clear the error status of a previously failed task, making it appear as if all subsequent tasks fail with the same error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions