Skip to main content
print this page

Workflow email node failing

· 2 min read
Fix Available
Fix Available
This bug has been fixed
Patch Available
Patch Available
This bug has a patch available for affected versions

After upgrading to v2.4, workflows created before the upgrade fails when triiggered to run.

Affected Versions: 2.4

Fix Version: 2.5

2.4*

Customers upgrading to 2.4 after February 26, 2024 does not require explicit patching as the fix will be part of the release artifacts.

Root cause(s)​

Amorphic introduced FIPS in v2.4. Subsequently, Glue jobs created as part of Amorphic functionalities introduced a new Default Argument '--enableFips'. This includes the Glue jobs for Workflow nodes.

Hence, workflows created post v2.4 will work perfectly as expected taking use of the new Default Argument. But workflows that were created before v2.4 will fail when triggered.

This is because, old Amorphic generated Glue jobs were not backfilled wth the new Default Argument.

Impact​

After upgrading to 2.4, when users try to trigger a workflow which was created before v2.4, the workflows will fail to execute properly as the nodes will fail. No impact will occur to any data as execution will fail early on.

Mitigation​

Fix available

Fix is available in Amorphic version 2.5. Please upgrade to the latest version to resolve this issue.

Patch available

Patch is available for Amorphic versions v2.4.

Please contact amorphic-support@cloudwick.com to patch your application.

Timeline​

gantt
    title Timeline
    dateFormat YYYY-MM-DD
    tickInterval 7day
    axisFormat %b-%d
    todayMarker off
    section Tracker
        %% update the ticket number and date of bug report
        CLOUD-4390 : done, 2024-02-23, 0d
    section Identification
        Reported : crit, des1, 2024-02-23, 0d
    section Mitigation
        %% Update number of days took for each step below
        Bug Fixed: crit, done, 2024-02-26, 1d
    section Delivery
        %% update the date of each step below
        testing complete: milestone, 2024-02-26, 0d
        patch avaialble: milestone, 2024-02-26, 0d
  • 2024-02-23: Bug reported/identified (CLOUD-4390)
  • 2024-02-26: Bug triaged
  • 2024-02-26: Bug fixed
  • 2024-02-26: Testing of patch on v2.4 is completed
  • 2024-02-26: Patch for v2.4 released