You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed a number of errors when syncing 240528.7d230cd-bimonthly on May 29 that started with Skipped '/vulpes/ngi/staging/240529.7d230cd-bimonthly' path due to this access issue: '/vulpes/ngi/staging/240529.7d230cd-bimonthly' is not a directory
This was a deployment that did not exist.
The syncing worked when the deploy_date in tasks/set-paths.yml was changed to the date the deployment was done.
The text was updated successfully, but these errors were encountered:
We noticed a number of errors when syncing
240528.7d230cd-bimonthly
on May 29 that started withSkipped '/vulpes/ngi/staging/240529.7d230cd-bimonthly' path due to this access issue: '/vulpes/ngi/staging/240529.7d230cd-bimonthly' is not a directory
This was a deployment that did not exist.
The syncing worked when the
deploy_date
intasks/set-paths.yml
was changed to the date the deployment was done.The text was updated successfully, but these errors were encountered: