Skip to main content

CLI Version

npx mapps --version
@mondaycom/apps-cli/4.8.0 linux-x64 node-v22.19.0

What I tried

Command:

npx mapps scheduler:create --verbose --print-command -a $APP_ID -s "0 * * * *" -n "execute-rules" --targetUrl "/execute-rules" -r 10 -b 60 -d "This execute rules hourly"

Result:
The request reaches the API but fails with 400 Bad Request.

[06:36:38.575] ERROR: Request failed with status code 400 - Bad Request - ERR_BAD_REQUEST - {"error":"Bad Request"}: undefined
[06:36:38.576] ERROR: scheduler_create
err: {
"type": "Error",
"message": "Invalid request",
...
}


Alternative attempt

Because the CLI --help shows a -u, --targetUrl=<value> flag, I tried this instead:

npx mapps scheduler:create --verbose --print-command -a $APP_ID -s "0 * * * *" -n "execute-rules" -u "/execute-rules" -r 10 -b 60 -d "This execute rules hourly"


Result
The CLI rejected the argument completely.

[06:45:14.622] ERROR: Unexpected argument: /execute-rules
See more help with --help

Environment

  • App ID: $APP_ID

  • CLI: @mondaycom/apps-cli/4.8.0

  • Node: v22.19.0

  • OS: Linux (x64) (docker container)

Summary of issue:

  • I deployed the app with live version and draft version, --targetUrl runs but produces a 400 Bad Request.
  • -u (short form, as shown in --help) is not recognized and throws Unexpected argument.

 

I was able to create the scheduler job by leaving out the retry (-r) and duration (-b) values — those caused the request to fail. After creation, the cronjob runs successfully, but note that it doesn’t use the Monday signing secret. The request comes with a Google-signed JWT instead, which needs to be validated against Google’s public keys (https://www.googleapis.com/oauth2/v3/certs, issuer https://accounts.google.com)