Push failed — what to check

When a push fails, the Activity stream shows a red Failed badge with an error category. This page maps error categories to fixes.

Find the failed push

Dashboard → Activity → filter by Status: Failed. Click any failed event to expand the full payload, error message, HTTP status code, and timing breakdown.

The event row tells you which site, which tokens, and which error category is at fault.

Error categories

auth_failed (HTTP 401)

The WP plugin rejected the HMAC signature. Causes:

• Cloned database: production database was copied to staging (or vice versa). Both sites now have the same api_secret, but Hubbee only registered one. The other site rejects all pushes.
  • Fix: Re-run Connect on the cloned site to get a fresh secret.
• Clock drift: WP server clock differs from Hubbee server clock by >5 minutes.
  • Fix: Run ntpdate or enable a time-sync service on the WP host.
• Plugin reinstalled with WP-CLI dropping data: the api_secret option was wiped.
  • Fix: Re-run Connect.

timeout (no response in 30 seconds)

The plugin’s REST endpoint didn’t respond before Hubbee’s timeout. Causes:

• WP server is overloaded (high traffic, slow database)
• A WP plugin (often a caching, security, or maintenance plugin) is blocking the request
• The wp-json permalinks are broken

Test:

curl -X POST https://your-site.example/wp-json/bz/v1/health -m 35

If this hangs, the issue is at the WP layer. See Plugin shows offline for the broader diagnostic.

network_error (no TCP connection)

Hubbee couldn’t reach the WP site at all. Causes:

• Site is offline (check homepage)
• DNS recently changed and propagation isn’t complete
• Cloudflare or similar WAF is blocking Hubbee’s IP

Hubbee’s outbound IPs are static. If a WAF is blocking us, allowlist the current Hubbee egress IPs published at hubbee.io/network.

validation_error (HTTP 400)

The plugin rejected the push payload as malformed. Causes:

• Token field type changed (e.g., text → richtext) but value still contains plain text without sanitization
• Token key contains invalid characters (only lowercase, digits, underscore allowed)
• Value exceeds 64 KB (Hubbee’s per-token limit)

Fix: Edit the token in the dashboard and re-save. Validation runs on save; only valid values can be pushed.

processed_with_errors (HTTP 200 but errors: [...])

Push succeeded technically, but specific tokens failed at the WP side. The error array shows per-token detail:

• "key": "hero_title", "error": "field_type_mismatch" → token field type doesn’t match what your Elementor/theme widget expects
• "key": "X", "error": "locked_by_other_user" → another team member has the token locked for editing
• "key": "X", "error": "cache_invalidation_failed" → push succeeded, but the cache plugin failed to flush. See Cache conflicts.

Retry behavior

Failed pushes are NOT auto-retried. Each push is a one-shot operation initiated by you (manually or scheduled).

If you fix the underlying issue and want to retry:

• From Activity: open the failed event → Retry. The push fires again with the same payload.
• From Tokens: edit any token → Save & Push. The current value of all tokens in that section is sent.

When to escalate

If pushes fail repeatedly with no clear category, or if the Activity stream shows a generic internal_server_error, open a support thread with:

• The failed event ID (from the URL when viewing the event detail)
• Site URL
• Approximate time of failure (ISO format with timezone)

We can look at server-side logs from your event ID alone.