We have added many useful tools over the years to help you troubleshoot all kinds of potential issues, many with their own UI:

  • If a piece of content is not pushed or pulled, we will always try to show this to the affected user and log it to Drupal. So, the best place to start is usually in the Drupal logs. If you see an error there that you can’t decipher, please reach out to us with the exact error message, the call stack, and a description of what you’re trying to achieve.
  • If an update is not arriving at another site, please open the content at the source site and open the Content Cloud tab (called “Content Repository” for on-premise customers). This tab shows the progress of the synchronization and allows you to see a list of all destinations and the status of the update per site. If there’s an issue you can expand the item in the list and click “Details” to see the exact request that we’ve made including the request and response body. In case of failures, the response body usually includes the exact error message and call stack from the remote site as well. You can also use this request information to retry the sync yourself e.g., with Postman.
    • We retry failed requests multiple times in a 24h timeframe to automatically recover from temporary failures.
  • If someone else reported an issue and you’re having difficulties finding the right log message, please enable our “Health” sub-module and navigate to Content > Sync Health > Entity Status. This list contains the status of all entities we’ve ever tried to push or pull. You can filter this list by entity type, flow, pool, sync status, and you can filter nodes by title to find the entity in question. This list includes the errors that were encountered when we tried to push or pull an item.

Please keep in mind that you always have manual updates as a workaround so that critical updates can still be published without our automation. This is important to consider when estimating the criticality of our service and when creating your WebOps playbook.