Stuck when run is triggered via API call but not on dashboard?

def generate_signed_url(blob_name, expiration_minutes=60):
    log.info(f"Generating signed URL for {blob_name}")
    blob = bucket.blob(blob_name)
    url = blob.generate_signed_url(expiration=timedelta(minutes=expiration_minutes))
    log.info(f"Signed URL: {url}")
    return url

def generate_signed_url(blob_name, expiration_minutes=60):
    log.info(f"Generating signed URL for {blob_name}")
    blob = bucket.blob(blob_name)
    url = blob.generate_signed_url(expiration=timedelta(minutes=expiration_minutes))
    log.info(f"Signed URL: {url}")
    return url

# Use Runpod base image
FROM runpod/base:0.4.0-cuda11.8.0

# Optional: Install extra Linux packages here if needed
# COPY builder/setup.sh /setup.sh
# RUN bash /setup.sh && rm /setup.sh

# Set working directory
WORKDIR /app

# Copy Python dependencies
COPY builder/requirements.txt .

# Install Python dependencies
RUN python3.11 -m pip install --upgrade pip && \
    python3.11 -m pip install --upgrade -r requirements.txt --no-cache-dir && \
    rm requirements.txt

# Copy your actual src code
COPY src/ .

# Start the worker
CMD ["python3.11", "-u", "handler.py"]

# Use Runpod base image
FROM runpod/base:0.4.0-cuda11.8.0

# Optional: Install extra Linux packages here if needed
# COPY builder/setup.sh /setup.sh
# RUN bash /setup.sh && rm /setup.sh

# Set working directory
WORKDIR /app

# Copy Python dependencies
COPY builder/requirements.txt .

# Install Python dependencies
RUN python3.11 -m pip install --upgrade pip && \
    python3.11 -m pip install --upgrade -r requirements.txt --no-cache-dir && \
    rm requirements.txt

# Copy your actual src code
COPY src/ .

# Start the worker
CMD ["python3.11", "-u", "handler.py"]

print("✅ Job completed successfully.")

print("✅ Job completed successfully.")

const requestConfig = {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${runpod.api_key}`,
  },
  body: JSON.stringify({
    input: {
      video_path,
      audio_path,
    },
  }),
};

const response = await fetch(`${runpod.endpoint}/runsync`, requestConfig);
const data = await response.json();

return data;

const requestConfig = {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${runpod.api_key}`,
  },
  body: JSON.stringify({
    input: {
      video_path,
      audio_path,
    },
  }),
};

const response = await fetch(`${runpod.endpoint}/runsync`, requestConfig);
const data = await response.json();

return data;

{
    "delayTime": 5150,
    "executionTime": 2775,
    "id": <job id>,
    "output": {
        "message": "Files processed, uploaded, and cleaned up successfully",
        "signed_url": "..."
    },
    "status": "COMPLETED",
    "workerId": "83kgwesbus3cfb"
}

{
    "delayTime": 5150,
    "executionTime": 2775,
    "id": <job id>,
    "output": {
        "message": "Files processed, uploaded, and cleaned up successfully",
        "signed_url": "..."
    },
    "status": "COMPLETED",
    "workerId": "83kgwesbus3cfb"
}

It is still bugged, but now it is stuck in progress even if I trigger it directly from the dashboard:

here is a recording.
https://app.canvid.com/share/fi_01JTFC00JSQMJPP236V39N3NKW

As you can see, in the code and even on the "progress output" it is not stuck on the "Done" but the status is in progress, however it seems that jobs triggered via API is now getting completed.. 

This is very weird

It is still bugged, but now it is stuck in progress even if I trigger it directly from the dashboard:

here is a recording.
https://app.canvid.com/share/fi_01JTFC00JSQMJPP236V39N3NKW

As you can see, in the code and even on the "progress output" it is not stuck on the "Done" but the status is in progress, however it seems that jobs triggered via API is now getting completed.. 

This is very weird