Skip to main content
print this page

Amorphic workflows sending incorrect status notifications

· 2 min read
Fix In Progress
Fix In Progress
Bug identified and fix is in progress
Workaround Available
Workaround Available
Temporary workaround available

Workflows sending incorrect notifications in scenarios mentioned below(Only when user is subscribed to workflow alerts)

  • when we have non-etl nodes in the workflow, even after the successful execution of the workflow system sends incorrect node failure email alert.
  • when the any node in the workflow failed, push notification shows error message and details but the status in the push notification says success.

Sample incorrect email notification details:

Title: Workflow 'abcd' encountered one or more node failures.

EventType: Node Execution Failure

ErrorMessage: Job run succeeded

Affected Versions: 2.1 2.0 1.14 1.13

Fix Version: 2.2

Root cause(s)​

In one of the use cases where the workflow is executed through an ETL job script then Amorphic is not recognizing the execution as valid and thereby sending a false error email indicating that this particular node got failed even though the node is successful. Status of the push notification block of code is marked as SUCCESS even though the workflow is failed.

Impact​

Users will receive incorrect failure email notifications even though all the nodes in the workflow were successfully executed. And receives incorrect push notification status for failed workflows.

Mitigation​

Fix InProgress

Fix will be available in Amorphic version 2.2. Please upgrade to 2.2 to resolve this issue once it is avaialble.

Temporary Workaround

Unsubscribe from the specific workflow alerts to not receive incorrect notifications.

Timeline​

gantt
    title Timeline
    dateFormat YYYY-MM-DD
    tickInterval 1day
    axisFormat %b-%d
    todayMarker off
    section Tracker
        %% update the ticket number and date of bug report
        CLOUD-3195 : done, 2023-03-29, 0d
    section Identification
        Reported : crit, des1, 2023-03-29, 0d
    section Mitigation
        %% Update number of days took for each step below
        Bug fixed: crit, done, 2023-04-02, 1d
    section Delivery
        %% update the date of each step below
        testing completed: milestone, 2023-04-07, 0d
  • 2023-03-29: Bug reported/identified (CLOUD-3195)
  • 2023-03-29: Bug triaged
  • 2023-04-03: Bug fixed
  • 2023-04-07: Testing completed.
  • 2023-06-01: Planned for Amorphic v2.2.