fix: address greptile review — network errors and status code handling

- Add !error.request check so Axios network errors (connection refused,
  server down) still show notifications — only suppress true JS runtime
  errors that have neither .response nor .request
- Use err.to_response() for VisitranBackendBaseException to preserve
  the exception's own HTTP status code (403, 404, etc.) instead of
  hardcoding 400

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: abhizipstack

backend/backend/core/routers/execute/views.py

@@ -67,6 +67,8 @@ def execute_run_command(request: Request, project_id: str) -> Response:
         return Response(data=_data)
     except (VisitranBaseExceptions, VisitranBackendBaseException) as err:
         logger.exception(f"[execute_run_command] DAG execution failed for file_name={file_name}")
+        if hasattr(err, 'to_response'):
+            return err.to_response()
         return Response(data=err.error_response(), status=status.HTTP_400_BAD_REQUEST)
     except Exception:
         logger.exception(f"[execute_run_command] Unexpected error during DAG execution for file_name={file_name}")

frontend/src/service/notification-service.js

@@ -61,7 +61,7 @@ function NotificationProvider({ children }) {
 
         // Skip notification for JS runtime errors (not API failures)
         // These have no useful info for the user — log them for debugging instead
-        if (error && !error.response && !message && !description) {
+        if (error && !error.response && !error.request && !message && !description) {
           console.error("[Runtime Error]", error);
           return;
         }