Question about catch inside .run effect

[Muhammed9991]

The .run effect has the following signature:

public static func run(
    priority: TaskPriority? = nil,
    operation: @escaping @Sendable (_ send: Send<Action>) async throws -> Void,
    catch handler: (@Sendable (_ error: Error, _ send: Send<Action>) async -> Void)? = nil,
    fileID: StaticString = #fileID,
    line: UInt = #line
  )

The catch is very useful if you have a single network request and in case it fails send a failure action. If it has multiple network requests each request might be handled slightly differently depending on the context. Is it recommended not to use catch in this case? Or are there any other ways around this issue.

Example:

case let .someButton:
   return .run { send in
      let networkRequest1 = try await ...
      let networkRequest2 = try await ... // Different failure then (.someFailureAction)
                    
     } catch: { error, send in
        await send(.someFailureAction(error))
     }

Only way I can think of solving this is to ignore the catch and do this:

case response(TaskResult<SomeModel>)
case response2(TaskResult<SomeModel>)

case let .someButton:
   return .run { send in
      await send(.response(TaskResult {  try await ...  })) //networkRequest1
      await send(.response2(TaskResult {  try await ...  })) //networkRequest2
                    
     } 

Then handle success and failure in the reducer as normal.