Skip to main content

Deployment Troubleshooting

Common deployment issues and how to resolve them.

Deployment Failed​

If a deployment fails:

  1. Check the deployment logs - Click the failed deployment in history to view detailed logs
  2. Identify the error - Look for error messages indicating what went wrong
  3. Common causes:
    • Database connection issues
    • File permission problems
    • Timeout during large transfers

Resolution:

  • Wait a few minutes and retry the deployment
  • If the issue persists, contact [email protected] with the deployment logs

Push to Production Button Disabled​

The "Push QA to Production" button may be disabled for several reasons:

ReasonSolution
QA not updatedPush Development to QA first
Deployment in progressWait for current deployment to complete

Changes Not Appearing After Deployment​

If your changes don't appear after a successful deployment:

  1. Clear the cache - Click the cache clear button on the target environment
  2. Hard refresh - Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) in your browser
  3. Check the correct environment - Ensure you're viewing the right URL
  4. Verify deployment completed - Check deployment history for success status

Deployment Taking Too Long​

Deployments typically complete within 1-5 minutes. If a deployment is taking longer:

  • Large content - Sites with many products or media files take longer
  • Database size - Large databases require more sync time
  • Network issues - Temporary connectivity problems can slow transfers
tip

For very large sites, deployments may take up to 15 minutes. If a deployment exceeds 20 minutes, contact support.

Magic Login Not Working​

If Magic Login fails to open or log you in:

IssueSolution
Popup blockedAllow popups for the Urumi dashboard
Session expiredRefresh the dashboard and try again
Loading spinner stuckWait a moment, or refresh and retry
WordPress login page shownYour magic link may have expired, generate a new one

Environment Out of Sync​

If your environments seem inconsistent:

  1. Pull from Production to Development to get the latest live content
  2. Make your changes in Development
  3. Push to QA for testing
  4. Push to Production when ready

Getting Help​

If you can't resolve a deployment issue:

  1. Note the deployment ID from the history table
  2. Capture any error messages from the logs
  3. Contact [email protected] with:
    • Your store name/slug
    • Deployment ID
    • Description of the issue
    • Screenshots if helpful