Skip to content

fix!: LDAP sync triggers multiple cron jobs in case an invalid sync interval is provided #1108

fix!: LDAP sync triggers multiple cron jobs in case an invalid sync interval is provided

fix!: LDAP sync triggers multiple cron jobs in case an invalid sync interval is provided #1108

Triggered via pull request October 8, 2024 19:18
Status Success
Total duration 15m 51s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Unable to query cache: Error: Cache service responded with 429
deploy-preview
Failed to save: Cache service responded with 429 during commit cache.
deploy-preview
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3.7.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/