> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/faq/solutions-and-how-tos/handling-github-deployment-errors-due-to-expired-duplocloud-tokens.md). # Handling GitHub Deployment Errors Due to Expired DuploCloud Tokens When deploying applications via GitHub Actions, deployments can fail if the DuploCloud API token used for authentication has expired. This guide explains how to resolve the issue and prevent it from recurring. ### Step 1: Confirm the Cause of the Failure Check your GitHub Actions workflow logs to verify that the deployment failure is due to an expired DuploCloud API token. Look for authentication errors referencing the token. ### Step 2: Generate a New API Token Follow the instructions in the [DuploCloud API Tokens documentation](https://docs.duplocloud.com/docs/access-control/api-tokens#permanent-api-tokens) to generate a new token. ### Step 3: Update GitHub Secrets or Environment Variables 1. Open your GitHub repository settings. 2. Navigate to **Secrets and variables** → **Actions**. 3. Update the relevant secret or environment variable with the new API token.
Field / ActionDescription
Secret NameThe name of the GitHub secret holding your DuploCloud token (e.g., DUPLO_TOKEN).
ValuePaste the newly generated DuploCloud API token.
### Step 4: Rerun the Workflow Once the token is updated, rerun the failed GitHub Actions workflow to complete your deployment. ### Step 5: Prevent Future Token Expiration Issues To avoid deployment interruptions:
ActionDescription
Set up token expiration alertsMonitor token expiration dates in advance.
Use permanent API tokensRecommended for CI/CD automation to reduce the need for frequent updates.
[Learn how to set up token expiration alerts](https://docs.duplocloud.com/docs/access-control/api-tokens#permanent-api-tokens). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.duplocloud.com/docs/automation-platform/faq/solutions-and-how-tos/handling-github-deployment-errors-due-to-expired-duplocloud-tokens.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.