Why am I getting GitHub deployment errors due to expired Duplo tokens?

Context When attempting to deploy applications through GitHub Actions, you may encounter deployment failures due to expired Duplo API tokens. These tokens are essential for authenticating deployment processes and need to be renewed periodically. Answer When your GitHub deployment fails due to an expired Duplo token, you'll need to update the token in your environment. Here's how to handle and prevent this issue: First, verify if the error is due to an expired Duplo token by checking the GitHub Actions logs If confirmed, generate a new API token following the instructions in the Duplo API Tokens documentation Update the token in your GitHub repository secrets or environment variables Rerun the failed GitHub Action workflow Preventing Token Expiration Issues To avoid deployment interruptions, you can set up monitoring alerts for token expiration: Please review the below duplo doc for setting up the notification. https://docs.duplocloud.com/docs/access-control/api-tokens#permanent-api-tokens It's recommended to set up token expiration alerts well in advance of the actual expiration date to ensure continuous deployment operations.