%3CLINGO-SUB%20id%3D%22lingo-sub-1815699%22%20slang%3D%22en-US%22%3ECancel%20and%20Rerun%20Tumbling%20Window%20Trigger%20Run%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1815699%22%20slang%3D%22en-US%22%3E%3CP%3E%5BFollowing%20material%20applies%20to%20Tumbling%20Window%20Triggers%20in%20Azure%20Data%20Factory.%20Learn%20more%20about%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-factory%2Fhow-to-create-tumbling-window-trigger%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETumbling%20Window%20Trigger%3C%2FA%3E%5D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20the%20newly%20released%20feature%2C%20you%20now%20have%20the%20capabilities%20to%20cancel%20Tumbling%20Window%20Trigger%20runs%20if%20the%20window%20is%20in%26nbsp%3B%3CEM%3ERunning%20%3C%2FEM%3Eor%26nbsp%3B%3CEM%3EWaiting%20on%20Dependency%3C%2FEM%3E%20state.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%20class%3D%22code-line%22%20data-line%3D%22165%22%3EIf%20the%20window%20is%20in%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3ERunning%26nbsp%3B%3C%2FEM%3Estate%2C%20cancel%20the%20associated%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3EPipeline%20Run%3C%2FEM%3E%2C%20and%20the%20trigger%20run%20will%20be%20marked%20as%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3ECancelled%3C%2FEM%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eafterwards%3C%2FLI%3E%0A%3CLI%20class%3D%22code-line%22%20data-line%3D%22165%22%3EIf%20the%20window%20is%20in%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3EWaiting%26nbsp%3B%3C%2FEM%3Eor%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3EWaiting%20on%20Dependency%3C%2FEM%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Estate%2C%20you%20can%20cancel%20the%20window%20from%20Monitoring%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22cancel-tumbling-window-trigger.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F229080iA076597072795F2F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22cancel-tumbling-window-trigger.png%22%20alt%3D%22cancel-tumbling-window-trigger.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20also%20rerun%20a%20cancelled%20window.%20The%20rerun%20will%20take%20the%20%3CEM%3E%3CSTRONG%3Elatest%3C%2FSTRONG%3E%26nbsp%3B%3C%2FEM%3Epublished%20definition%20of%20the%20trigger%3B%20and%20dependencies%20for%20the%20specified%20window%20will%20be%20re-evaluated%20upon%20rerun.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22rerun-tumbling-window-trigger.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F229081i2681F97C8B4B12AD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22rerun-tumbling-window-trigger.png%22%20alt%3D%22rerun-tumbling-window-trigger.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECombining%20these%20two%20capabilities%20give%20you%20a%20powerful%20way%20to%20resolve%20the%20hanging%2Fblocking%20dependencies%20view.%20Imagine%20the%20following%20scenario%3A%20TWT-B%20depends%20on%20TWT-A%2C%20and%20for%20some%20reasons%20TWT-A%20has%20been%20consistently%20failing%20lately.%20To%20unblock%20downstream%20work%20flows%2C%20you%20decided%20to%20remove%20TWT-A%20from%20TWT-B's%20dependency%20list.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInstead%20of%20stopping%20and%20restarting%20TWT-B%2C%20you%20can%20now%20take%20following%20steps%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ECancel%20all%26nbsp%3B%3CEM%3EWaiting%20on%20Dependency%3C%2FEM%3E%20runs%20of%20TWT-B%20(these%20are%20the%20windows%20waiting%20for%20TWT-A%20to%20finish)%3C%2FLI%3E%0A%3CLI%3EEdit%20and%20publish%20new%20trigger%20definitions%20of%20TWT-B%20to%20remove%20dependencies%3C%2FLI%3E%0A%3CLI%3ERerun%20the%20cancelled%20runs%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3ESince%20the%20rerun%20will%20take%20the%20new%20definition%2C%20it%20will%20by-pass%20the%20blocking%20TWT-A%2C%20and%20enable%20downstream%20workflow%20to%20continue%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1815699%22%20slang%3D%22en-US%22%3E%3CP%3EUse%20the%20combination%20of%20Rerun%20and%20newly%20introduced%20Cancelling%20of%20Tumbling%20Window%20Trigger%20run%20to%20resolve%20hanging%2Fblocking%20dependencies%20issue%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1815699%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Data%20Factory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20ETL%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

[Following material applies to Tumbling Window Triggers in Azure Data Factory. Learn more about Tumbling Window Trigger]

 

With the newly released feature, you now have the capabilities to cancel Tumbling Window Trigger runs if the window is in Running or Waiting on Dependency state. 

 

  • If the window is in Running state, cancel the associated Pipeline Run, and the trigger run will be marked as Cancelled afterwards
  • If the window is in Waiting or Waiting on Dependency state, you can cancel the window from Monitoring

cancel-tumbling-window-trigger.png

 

You can also rerun a cancelled window. The rerun will take the latest published definition of the trigger; and dependencies for the specified window will be re-evaluated upon rerun.

rerun-tumbling-window-trigger.png

 

Combining these two capabilities give you a powerful way to resolve the hanging/blocking dependencies view. Imagine the following scenario: TWT-B depends on TWT-A, and for some reasons TWT-A has been consistently failing lately. To unblock downstream work flows, you decided to remove TWT-A from TWT-B's dependency list. 

 

Instead of stopping and restarting TWT-B, you can now take following steps:

  1. Cancel all Waiting on Dependency runs of TWT-B (these are the windows waiting for TWT-A to finish)
  2. Edit and publish new trigger definitions of TWT-B to remove dependencies
  3. Rerun the cancelled runs

Since the rerun will take the new definition, it will by-pass the blocking TWT-A, and enable downstream workflow to continue