Skip to main content
Question

Failed to save hub. Please try again later.

  • August 18, 2026
  • 1 reply
  • 11 views

Having a really tough time troubleshooting an issue where ANY change to a Box hub throws “Failed to save hub.” when attempting to save. 

This just started happening 6 days ago and I can not find ANY information on this. At best AI and the articles mostly suggest to contact support if basic troubleshooting fails. 

 

Problem is that I have no idea how to get in contact with Box’s actual support team from within the website. 

1 reply

Jey Bueno Box
Forum|alt.badge.img
  • Community Manager
  • August 18, 2026

👋 Hi ​@PHMadmin, thanks for reaching out, and I’m sorry to hear you’re running into issues saving changes to your Box Hub.


Here are the most common causes and troubleshooting steps to help isolate and resolve the error:
 

1. Check permissions and enterprise policies

  • Enterprise & Shield settings: Since this started recently, check with your Box Admin to verify whether any enterprise-wide settings or Box Shield policies were updated (e.g., restrictions on publishing/editing Hubs or changes to collaborator permissions).
  • Hub collaborator role: Make sure your account still holds Editor, Co-owner, or Hub Creator permissions on the specific Hub.
     

2. Browser & session troubleshooting

  • Incognito/private window: Open your Hub in an incognito/private browser window or try a different browser to rule out stale cache, cookies, or browser extensions (such as ad blockers).
  • Re-authenticate: Fully log out, clear your browser cache, and log back in through your organization’s login/SSO portal to refresh your session tokens.
     

3. Scope the issue (specific Hub vs. all Hubs)

  • Try creating a new test Hub and making minor edits.
    • If saving works on a new Hub, the original Hub likely has a specific corrupted element, block, or broken reference.
    • If saving fails across all Hubs, the issue is likely tied to user account permissions or enterprise-level settings.

 

If the issue persists after trying these steps:


Thank you!