PYX

Troubleshooting

Common console, script, and funding issues and how to resolve them.

Task stuck in error

Possible causes:

  • Script compile error
  • 5 runtime errors within 10 seconds
  • Restart failure during script edit

Check logs first. If error follows script edit, verify script compiles and strategy callbacks are bounded in runtime.

Script edit did not apply immediately

This can happen when the task is not currently loaded in memory. In this case script changes are saved but not live reloaded.

Task stays in draining

draining is the normal wind-down state. The task stops opening new exposure, but it keeps sells, order updates, exchange events, and resolution handling active until shutdown conditions are met.

A draining task moves to stopped only after:

  • There are no open positions that still count as active
  • There are no active or in-flight orders

If auto_redeem_on_resolve = true, resolved positions still wait for the normal auto-redeem flow before the task finishes stopping.

Use Force Stop only when you need immediate teardown and are willing to market-close open positions.

Bridge status seems delayed

Bridge flows are asynchronous across chains. The UI polls status every 5 seconds. PROCESSING and SUBMITTED can take time depending on source/destination conditions.

Activate Funds button not visible

The button appears when your Safe has at least 2 USDC (native) detected on Polygon.

Detection is periodic (15-second polling), so recent transfers can take a short time to surface.

Export returned few or no rows

  • Ensure you selected the correct task
  • For market trades, ensure the selected market actually has fills
  • Confirm time period had activity

On this page