Troubleshooting
What the common connector errors mean and how to resolve them.
| Symptom | Cause | Fix |
|---|---|---|
| Connection test fails to reach the function | The function is not deployed, or was deployed with JWT verification on. | Redeploy with --no-verify-jwt and confirm aemc-content is Active. |
| AEMC_UNAUTHORIZED / signature rejected | The shared secret or connection ID does not match. | Re-set both secrets in Supabase and update the connection. |
| AEMC_CLOCK_SKEW | The request timestamp is outside the 300-second window. | Retry; if it persists, check the clock on the machine issuing the request. |
| Tables report unavailable (42P01) | The configured table name does not exist in your project. | Point AEMC_*_TABLE at your real tables, then Refresh schema. |
| Fields report unavailable (42703) | The configured column does not exist on the row. | Set the matching AEMC_*_COLUMN candidate list, then Refresh schema. |
| Save stays at Verification pending | The read-back could not confirm one of the written fields. | Check the capability matrix — unsupported axes are not verified — then retry the save. |
| Schema drift warning | Your tables or columns changed after the connection was set up. | Use Check schema drift, then Refresh schema to re-learn the mapping. |
Safe diagnostics
The connector exposes signed, read-only diagnostics that return column names and value kinds only — never your column values, article bodies or secrets.
Never send secrets to support
No support request will ever ask for your service-role key, shared secret or a Vault identifier.