hey, we are using descope cicd github template to deploy between our staging and production project. There are changes coming through but not everythings and we don't know why. For example, the container width in staging is set to 100% but does not get updated in production. Style theme also not getting updated. Any recommendation for debugging this issue?

Troubleshooting CI/CD Deployment Issues Got it — you're seeing partial deployments where some changes sync but others like container width and style themes don't, right? Common Causes 1. Management Key Permissions — Verify your management key has access to both staging and production projects 2. Export/Import Exclusions — Check if specific items are being excluded during import. The import process allows excluding items like

styles

,

flows

, or project-specific settings Debugging Steps 1. Check GitHub Actions Logs — Review the workflow logs to see if any errors occur during export/import 2. Manual Export Comparison — Export both projects manually from Project Settings and compare the JSON files to identify missing configurations 3. Verify Secrets Handling — If using connectors or OAuth providers, ensure

PLACEHOLDER_VALUE

entries are handled correctly in your configuration • Test with a manual import to isolate if the issue is with the CI/CD template or the export/import process itself • Ensure your management key scope includes both projects you're syncing between Github CI/CD Descope Environments | Descope Documentation Export Project | API Reference | Descope Documentation Managing Environments | Descope Documentation Managing Environments | Descope Documentation GitLab CI/CD Descope Environments | Descope Documentation

Seems like the deploy is skipped even though the PR detected many changes. This is not the first time it happens, can I get some guidance here?

Deploy Skipped Despite Changes This suggests the CI/CD template's validation logic isn't detecting the changes as deployment-worthy, even though files were modified. Check Workflow Conditions 1. Review GitHub Actions logs — Look for conditional checks that might be skipping deployment steps 2. Validate file paths — The template may only trigger on specific file patterns or directories

# Check if your workflow has path filters like:
on:
  push:
    paths:
      - 'project/__'
      - '!__.md'

Common Skip Scenarios 1. Branch protection — Deployment only runs on specific branches (main/production) 2. File type exclusions — Documentation or non-configuration files might not trigger deploys 3. Validation failures — Export validation step fails silently, causing deployment to skip Debugging Steps 1. Check the "Actions" tab in your GitHub repo for the full workflow execution details 2. Look for conditional statements in the workflow that evaluate to false 3. Verify your staging project export is valid by running a manual export/import test The workflow logs should show exactly which condition caused the deployment to skip. Can you share what the Actions log shows for the skipped deployment step?