Follow Avox Docs on Google
Pick Avox Docs as a preferred source and Google shows these pages more often when you search for help with Avox.
Follow Avox Docs on Google
Pick Avox Docs as a preferred source and Google shows these pages more often when you search for help with Avox.
Start on the app's page (Connections, then Apps, then the app): its status, the last problem with its code, and the log usually say what happened. Test connection checks the app again in a second.
Avox isn't ready to connect that app yet (AVX-3682). Use another app for now, or ask hello@theavoxai.com when it will be ready.
AVX-3686: copy the keys again (whole, no spaces), check that live and test match, and for a Stripe restricted key give it Checkout Sessions and Refunds (write).
The app stopped accepting Avox's access (AVX-3692): Avox was removed in the app, the app was uninstalled, a password or security setting changed, or the access ran out. Click Reconnect and sign in with the same account. Steps that use the app are skipped until then.
Several calls in a row failed on the app's side. Open the log, filter by Failed, and open an entry to read the app's own reason. It goes back to Connected by itself once a call works.
For Razorpay, Stripe, PayPal and WooCommerce, check Instant updates on the app's page:
If updates fail the check, the page counts them. After you change the secret, the count starts over. Updates that arrive twice are kept once.
Open the app's log and the failed entry. Common codes:
Entries are kept as long as your webhook log retention on Compliance (AVX-3710). The log shows up to 90 days at a time; pick an earlier range to see older ones.
Disconnecting deletes Avox's saved access and keeps the log. If you see AVX-3697, Avox is disconnected but the app didn't confirm it: remove Avox in the app's settings for connected apps too.
Still stuck? Email hello@theavoxai.com with the code and the time it happened.
Last updated