Issue with Worker Initiation Error Leading to Persistent "IN_PROGRESS" Job Status
Hi All,
While testing the endpoint, I observed that when initiating a job with an empty input in the request body (using {"input": {}} or an empty JSON {}), the worker fails to start successfully. Despite this, the job status continually displays as "IN_PROGRESS".
This problem persists without reaching a resolution or a timeout state, necessitating manual intervention to cancel the job. The log output indicates an error message: "Job has missing field(s): input." However, the job status doesn't reflect this error and remains indefinitely in progress.
I am including a snippet of the log output for reference. Thank you in advance for looking into this issue.
While testing the endpoint, I observed that when initiating a job with an empty input in the request body (using {"input": {}} or an empty JSON {}), the worker fails to start successfully. Despite this, the job status continually displays as "IN_PROGRESS".
This problem persists without reaching a resolution or a timeout state, necessitating manual intervention to cancel the job. The log output indicates an error message: "Job has missing field(s): input." However, the job status doesn't reflect this error and remains indefinitely in progress.
I am including a snippet of the log output for reference. Thank you in advance for looking into this issue.
