## **🔍 Overview**

If your WordPress site appears as **Active** in Atlas Coworker but returns an error such as *"The operation wordpress-get-current-user is not available for wordpress"* when you attempt to run operations, your connector is in a broken state. This is a known issue affecting WordPress and custom-MCP connectors in Coworker, and it does not automatically resolve on its own.

This article explains what causes the error, which sites are affected, and the steps you can take right now to restore functionality.



## **⚠️ What This Error Means**

An **Active** status only confirms that a connection record exists — it does not guarantee the connector is fully functional. The error message indicates that the gateway routing between Coworker and your WordPress site is broken, meaning Coworker cannot execute any WordPress operations through that connector, even though the connection appears healthy on screen.

Common symptoms include:

- Connection status shows **Active** but all WordPress operations fail immediately.
- Error messages reference operations such as *wordpress-get-current-user*, *wordpress-get-posts*, or similar WordPress actions being unavailable.
- Bulk publish or content operations do nothing or return instant errors.

## **🌐 Does This Affect All My WordPress Sites?**

Not necessarily. Each WordPress connector is independent, so the issue is tied to the specific site where the error appears. However, if you connected multiple WordPress sites around the same time using the same workflow, it is worth checking each one individually, as the underlying routing problem can affect any connector created through the broken setup flow.

To check your other sites, navigate to **Coworker** in the left sidebar and review each WordPress connection. Attempt a test operation on each one to confirm whether it succeeds or returns a similar error.



## **🛠️ Steps to Resolve the Error**

1. **Go to Coworker.** In the left sidebar, click **Coworker**.
2. **Locate the affected connection.** Find the WordPress site that is returning the error (for example, longislandcustomblinds.com).
3. **Remove the broken connector.** Disconnect or delete the existing WordPress connection for that site. Do not simply reconnect on top of the existing record — the old broken record must be removed first.
4. **Reconnect your WordPress site.** Use the connector setup flow to add the site again from scratch. Follow all prompts through to completion. Ensure you reach the final confirmation step — an incomplete setup is one of the most common causes of this error.
5. **Test the connection immediately after reconnecting.** Run a simple operation, such as fetching the current user or retrieving a post, to confirm the connector is working before relying on it for bulk tasks.

## **💡 Tips to Prevent This Issue**

- **Complete the full setup flow.** Do not close the connector window or navigate away before the setup confirms completion. Partial connections can appear Active while being non-functional.
- **Use the direct connector setup link.** If the AI Agent or an in-platform prompt gives you a WordPress connection link that leads to an unexpected page, do not use it — navigate to Coworker manually via the left sidebar instead.
- **Avoid white-label domain URLs during setup.** If your workspace is accessed via a white-label domain, connector setup redirects may fail. Use the primary Search Atlas platform URL when connecting WordPress sites.
- **Check each site individually.** If you manage multiple WordPress sites in one workspace, test each connector separately after any reconnection to confirm all are working.

## **🔄 Current Status**

The Search Atlas engineering team has identified the root causes behind broken WordPress connectors in Coworker and fixes are actively in development. These include improvements to the connector setup flow, resolution of gateway routing errors, and cleanup of incomplete connection records. You do not need to wait for the fix to be deployed — following the reconnection steps above will restore functionality for your site now.



## **🙋 Still Need Help?**

If you have followed the steps above and your WordPress connector is still returning errors, or if you are unsure whether additional sites in your workspace are affected, our team can investigate your specific connection records directly.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.