Long-running Serverless Requests on Runpod Execute Twice, Doubling Billing Costs
I’m experiencing an unexpected behavior when running long requests (with data payloads around 200k samples) (Clustering using berTopic). After the job finishes and posts the results, it unexpectedly triggers another execution of the same request. This behavior causes the job to run twice, effectively doubling my costs. Notably, when I run similar jobs with smaller payloads (e.g., 10k or 20k samples), they execute normally without any duplicate runs.
