Params attributes are being ignored when submitted to workflow/launch API end point

Ask for help
1

Greetings,

I had a working example of submitting a pipeline job using the Seqera API (https://api.cloud.seqera.io/workflow/launch?workspaceId=XXXX). It was last run successfully on 2025-05-17. In the JSON payload, I used the params attribute to pass parameters as shown below:

payload = {
    "launch": {
        "computeEnvId": "XXXXXXXXX",
        "runName": "test_2",
        "pipeline": "https://github.com/XXXX/myapp-test",
        "workDir": "s3://myapp-nextflow-scratch/workspace/",
        "revision": "main",
        "params": {
            "sleeptime": 5,
            "nlines": 10,
            "input": "s3://myapp-job-data/test_job_1/inputs/fog_wikipedia_summary.txt",
            "outputdir": "s3://myapp-job-data/test_job_1/outputs/"
        }
    }
}

When trying to run this same example today, it appears that the params are being ignored and I get an error that Both --input and --outputdir parameters must be provided. If I reformat the params as a paramsText string, the workflow runs fine.

Am I going nuts, or is the params attribute no longer supported? This issue seems very similar to this issue from last year.

Thanks,
James