Requests on Runpod Execute Twice, Doubling Billing Costs
I am experiencing unexpected behavior when running BerTopic clustering jobs. After the job finishes and posts the results, it unexpectedly triggers another execution of the same request. This results in the job running twice, effectively doubling my costs.
This issue occurred previously, but it was resolved. However, it has now reappeared.
This issue occurred previously, but it was resolved. However, it has now reappeared.
