---
title: "Confluence page saving fails with spinning wheel when Scaffolding is enabled"
canonical: "https://support.appfire.com/space/SUPPORT/3425927413/Confluence%20page%20saving%20fails%20with%20spinning%20wheel%20when%20Scaffolding%20is%20enabled"
format: markdown
---
## Summary

This article addresses an issue where enabling the **Scaffolding Forms & Templates** app causes Confluence page saving to fail, resulting in an infinite spinning wheel. This behavior can occur even if the app is correctly licensed and recently updated. 

## Symptoms

- When attempting to save or publish a Confluence page, the interface displays a continuous spinning wheel.
- The page never completes the save action, and any new data entered is not preserved.
- The issue is isolated to when the Scaffolding app is enabled; disabling the app allows pages to save normally.
- Creating a new space or page also results in an infinite spinning wheel.

## Environment

- **Product:** Scaffolding Forms & Templates for Confluence
- **Platform:** Data Center
- **Confluence version**: 8.5.15
- **Scaffolding version:** 9.2.9

## Diagnostics

Review the Confluence application logs (`atlassian-confluence.log`). You may see errors similar to the following, indicating a missing service dependency:

```
java.lang.RuntimeException: service matching filter=[(objectClass=com.servicerocket.confluence.randombits.metadata.MetadataManager)] unavailable. Listener: net.customware.confluence.plugin.scaffolding.listener.ScaffoldingMacroEventListener event: com.atlassian.confluence.event.events.content.page.PageUpdateEvent
...
Caused by: org.eclipse.gemini.blueprint.service.ServiceUnavailableException: service matching filter=[(objectClass=com.servicerocket.confluence.randombits.metadata.MetadataManager)] unavailable
```

Additionally, browser console logs may show failed POST requests to analytics or content endpoints:

```
Fetch failed loading: POST "https://<your-confluence-url>/rest/analytics/1.0/publish/bulk"
```

## Cause

The primary cause identified in this case was the disabling of a required dependency **ServiceRocket Utility Library**. The Scaffolding app relies on the **ServiceRocket Utility Library** (a bundled dependency) to manage metadata and other core functions. If this library is disabled or fails to initialize, Scaffolding cannot complete the page-save event, leading to a timeout or "stuck" thread in the Confluence UI.

## Resolution

### Use Case 1: ServiceRocket Utility Library is disabled

The most common cause for this specific "spinning wheel" behavior is that the required utility library has been manually disabled or failed to start.

1. Log in to Confluence as an Administrator.
2. Navigate to **Administration** (cog icon) > **Manage apps**.
3. Select **All apps** from the dropdown menu.
4. Search for **ServiceRocket Utility Library**.
5. If the status is **Disabled**, click **Enable**.
6. Once enabled, try to edit and save a page to verify the fix.

---

### Use Case 2: Corrupted plugin cache

If the utility library is enabled but the issue persists, the plugin system cache may be corrupted.

1. **Shutdown** the Confluence instance.
2. Create a temporary backup of the following directories located in the `<confluence-home>` directory:
  - `bundled-plugins`
  - `plugins-cache`
  - `plugins-osgi-cache`
  - `plugins-temp`
3. **Delete** the contents of these four directories (they will be recreated on startup).
4. **Restart** Confluence.
5. Verify if the Scaffolding app and page saving are functioning correctly.

> ℹ️ There will be some downtime since the Confluence instance needs to restart.

---

### Use Case 3: App reinstallation

If the above steps do not work, a clean reinstallation of the app may be required.

1. Navigate to **Manage apps**.
2. Locate and **Uninstall** both **Scaffolding Forms & Templates** and **ServiceRocket Utility Library**.
3. Use the **Find new apps** section to reinstall **Scaffolding Forms & Templates**.
4. Ensure the license is correctly applied and the app status is **Active**.

> ⚠️ Escalation:
> ⚠️ 
> ⚠️ If none of the above steps work and the issue still persists, raise a support ticket with the support.zip logs attached.