Deployment Failed

Quick Diagnosis

When you see “Deployment failed” in execution logs, start here:

1. Check error message in execution logs
2. Verify store credentials
3. Confirm theme ID exists
4. Check for API rate limits
5. Review file sizes

Common Errors & Solutions

“Unauthorized” or “Invalid credentials”

Cause: Store OAuth token expired or app was reinstalled.

Solution:

1. Go to Stores page
2. Find the store with issues
3. Click “Reconnect”
4. Complete OAuth flow in the popup
5. Retry deployment

---

“Theme/repo mismatch”

Symptoms: Execution aborts with Theme/repo mismatch: only X% of section/block types... exist in this repo.

Cause: The target theme on your store is a different theme than the one in your repo. If the workflow proceeded, content merge would corrupt the target theme by combining settings from one theme with sections from a completely different one.

Solution:

1. Confirm which theme the workflow’s repo contains
2. In Shopify Admin, identify which theme matches that repo
3. Update the Deploy / Content Merge / Store Matrix block to target the correct theme ID

This guard cannot be bypassed from the UI — it’s intentional.

---

“Theme not found” or “Invalid theme ID”

Cause: Theme ID doesn’t exist, was deleted, or belongs to a different store.

Solution:

1. Shopify Admin → Online Store → Themes → “…” → “Edit code”
2. Copy the numeric ID from the URL
3. Update the Deploy block with the correct ID, or use new to create a fresh theme

---

“GitHub API rate limit exceeded”

The app downloads the entire repository as a single archive to avoid this. If you still see this error, wait a few minutes and retry.

---

“Shopify API rate limit exceeded”

Solution:

1. Wait 5–10 minutes and retry
2. Reduce parallel deployments if using Store Matrix
3. Contact support for high-volume adjustments

---

“File too large” or “Asset exceeds size limit”

Individual assets > 20MB will fail.

Solution: Optimize images (use WebP), move videos to Shopify CDN or external hosting, subset fonts.

---

“Theme locked by another process”

Wait 2–3 minutes and retry. If it persists for more than 10 minutes, contact support.

---

Deploy on Push stopped triggering (no execution on git push)

Symptoms: Pushing to your repository no longer starts a workflow. No new executions appear, and GitHub shows no recent webhook deliveries. The repository still appears connected in Deployify.

Cause: The GitHub App lost access to the repository — for example, the app was reinstalled, repository access was changed from “All repositories” to “Only select repositories”, or the repo was transferred/renamed. Deployify keeps the saved connection record, so the repo can still look connected even though GitHub no longer sends push events for it.

Solution:

1. On GitHub, go to Settings → Applications → Installed GitHub Apps → Deployify → Configure
2. Under Repository access, confirm the repository is included (re-select it if missing) and save
3. In Deployify, open the Repositories page — repos the app can no longer access are flagged with an “Access lost” warning
4. Re-add the repository if needed, then re-save any workflow that references it
5. Push a test commit to confirm the deploy triggers

Prevention: When reinstalling or reconfiguring the GitHub App, prefer “All repositories” access, or double-check the selected repository list includes every repo used by a workflow.

Prevention Checklist

Before deploying:

• Backup created (use Backup block)
• Store credentials valid
• Theme ID verified in Shopify admin
• No syntax errors in theme files
• Large assets optimized (< 20MB each)

Getting Help

1. Open the execution details and download the logs
2. Note your store domain
3. Describe your workflow (blocks and order)
4. Contact support via in-app chat or erik@paxsolutions.io