Common Issues

Even with a robust automation engine, external blockchain factors can sometimes cause a Chain to fail or pause. This guide outlines the most frequent issues users encounter and provides specific steps to resolve them.

1. Chain Status: "Failed (Slippage Exceeded)"

Symptom Your Source Market resolved correctly, but the system did not purchase the target position. The status log shows "Slippage Exceeded."

Cause The price of the target shares changed rapidly between the moment the trigger fired and the moment the transaction was mined. The price moved beyond the "Max Price" limit you set in your Chain configuration.

Solution

• Adjustment: When building a Chain for highly volatile events (like live sports), increase your Slippage Tolerance to 2% or 3%.

• Retry: You cannot "retry" the specific failed automation, but your funds are safe. The system stopped before buying at a bad price. You can manually execute the trade on the dashboard.

2. Chain Status: "Failed (Insufficient Gas)"

Symptom The Chain failed to execute, and the error log indicates "Out of Gas" or "Insufficient Funds for Gas."

Cause While your trade is denominated in USDC, the transaction fee on the Polygon network must be paid in MATIC. Your wallet does not have enough MATIC to pay the network validators.

Solution

• Top Up: Ensure you always keep at least 1 to 2 MATIC in your wallet.

• Note: PolyOrbit cannot deduct gas fees from your USDC balance. This is a blockchain protocol rule.

3. Session Key Expired

Symptom The dashboard shows your Chain is "Paused" or "Inactive," and you cannot deploy new strategies.

Cause For security reasons, Session Keys have a fixed expiration date (default is 7 days). If you do not renew the key before it expires, PolyOrbit loses the permission to execute trades on your behalf.

Solution

• Re-Authenticate: Click the "Enable Automation" button on the dashboard and sign a new session transaction with your wallet.

• Monitor: Enable Telegram notifications to receive alerts 24 hours before your session expires.

4. Delayed Execution

Symptom The event (e.g., a football match) has ended, but the Chain is still in "Waiting" status.

Cause PolyOrbit relies on the official resolution data from the Polymarket Oracle (UMA). Sometimes, there is a delay between the real-world event concluding and the oracle officially verifying the result on-chain.

Solution

• Patience: The system will execute the moment the result is finalized on the blockchain. Do not manually intervene unless the delay exceeds 4 hours.