Automatic redeployments continue to run in GitHub Actions despite being completed in DigitalOcean

I am trying to use the digitalocean/app_action/deploy@v2 GitHub Action to automate the deployment of our development environment whenever a new image is pushed to our GitHub Container Registry.

Before I used the action I would have to manually go to the App Platform project and select Actions > Deploy. It would then grab the most recent development tag for the image and re-deploy it. This always worked and hasn’t caused us any issues.

I began using the digitalocean/app_action/deploy@v2 GitHub Action and had this step added after the image was pushed to the GitHub Container Registry:

  deploy_to_development:
    name: Deployment to DigitalOcean App Platform development environment
    needs: [release_management, push_to_registry]
    runs-on: ubuntu-latest
    steps:
      - name: Deploy to DigitalOcean App Platform (development)
        uses: digitalocean/app_action/deploy@v2
        with:
          token: ${{ secrets.DIGITALOCEAN_TOKEN }}
          project_id: ${{ vars.DIGITALOCEAN_PROJECT_ID }}
          app_name: ${{ vars.DIGITALOCEAN_APP_NAME }}

It would run and start returning the following log statements:

app "_______" already exists, updating...
wait for deployment to finish
deployment is in phase: PENDING_BUILD
deployment is in phase: BUILDING
deployment is in phase: DEPLOYING
deployment is in phase: ACTIVE

After the final phase, ACTIVE, the action would continue to run upwards of 5+ minutes without any changes. While it was running I went to the DigitalOcean App Platform project and verified in the activity section that the deployment was live and there was a checkmark next to both the build and deploy logs. In this past example the image was the same, so the deployment (per DigitalOcean’s logs) only took 1 second.

I didn’t want to waste our GitHub Action minutes so I would cancel it manually after 10+ minutes of running. It appears to be hanging after the deployment is done in GitHub Actions. How can I resolve this or is this an issue with DigitalOcean’s deploy action?