Gulp series execution limits during task failure

Task Orchestration Behavior

Gulp utilizes series() and parallel() to manage asynchronous task composition. In a sequential chain, the orchestrator relies on the return of a Stream, Promise, or callback to determine when to proceed to the next task.

Failure Handling Constraints

When a task within a series() block fails—such as by returning a rejected promise or throwing an error—the orchestrator stops the execution of all subsequent tasks in that specific chain. This behavior ensures that dependent tasks do not run on corrupted or incomplete data.

However, there is uncertainty regarding the state of the process when mixing these compositions. If a series() block is nested inside a parallel() block, the failure of the series only affects its own internal sequence, while sibling tasks in the parallel group continue.

• Does Gulp provide a built-in mechanism to trigger a specific "cleanup" task only when a series() chain is interrupted by an error?
• Is there a way to force the execution of a final task in a series regardless of whether previous tasks succeeded or failed?