Issue Summary

Scheduling pipelines using the API is not working as expected. Updating an existing cron via the API does not apply the new pattern — the old cron pattern is retained.

Steps to Reproduce

• Create a cron job via API POST call with "cron_pattern": "0 3 0 * * ? *".

• Update the cron job via PUT to change the pattern to "cron_pattern": "0 1 0 * * ? *" (modifying the <min> field).

• Observe that the change is not applied

Expected Results

The cron pattern should be updated to:
"cron_pattern": "0 1 0 * * ? *"

Actual Results

The cron pattern remains:
"cron_pattern": "0 3 0 * * ? *"

Workaround

Deleting the existing cron job and creating a new one with the desired pattern succeeds. Looking at the Bitbucket API documentation you shared, I can see that the PUT endpoint for updating schedules does NOT explicitly list cron_pattern as a supported field in the request body. By default it supports enabled (boolean) and type (string). could be the reason the update operation silently fails in the backend even though the API responds with a 200 OKstatus, the changes are not actually applied.

please delete the existing cron job and create a new one using a POST call with the desired schedule. This should work as expected.