fix: improve protocol error handling in sendTelegram and fix test

- Updated sendTelegram to properly handle protocol errors by checking isProtocolError flag before creating new WorkflowError
- Fixed test to use Web3TelegramWorkflowError instead of WorkflowError from @iexec/dataprotector
- Ensures protocol errors are properly detected and re-thrown with isProtocolError flag set

Author: abbesBenayache

src/web3telegram/sendTelegram.ts

@@ -305,7 +305,14 @@ export const sendTelegram = async ({
       taskId,
     };
   } catch (error) {
+    // Protocol error detected, re-throwing as-is
+    if ((error as any)?.isProtocolError === true) {
+      throw error;
+    }
+    // Handle protocol errors - this will throw if it's an ApiCallError
+    // handleIfProtocolError transforms ApiCallError into a WorkflowError with isProtocolError=true
     handleIfProtocolError(error);
+    // For all other errors
     throw new WorkflowError({
       message: 'Failed to sendTelegram',
       errorCause: error,

tests/e2e/sendTelegram.test.ts

@@ -256,7 +256,7 @@ describe('web3telegram.sendTelegram()', () => {
 
       // Pass the modified options to IExecWeb3telegram
       const invalidWeb3telegram = new IExecWeb3telegram(ethProvider, options);
-      let error: WorkflowError | undefined;
+      let error: Web3TelegramWorkflowError | undefined;
 
       try {
         await invalidWeb3telegram.sendTelegram({
@@ -265,10 +265,10 @@ describe('web3telegram.sendTelegram()', () => {
           telegramContent: 'e2e telegram content for test',
         });
       } catch (err) {
-        error = err as WorkflowError;
+        error = err as Web3TelegramWorkflowError;
       }
 
-      expect(error).toBeInstanceOf(WorkflowError);
+      expect(error).toBeInstanceOf(Web3TelegramWorkflowError);
       expect(error?.message).toBe(
         "A service in the iExec protocol appears to be unavailable. You can retry later or contact iExec's technical support for help."
       );