How can we help?

If changes to an AI Employee, workflow, business process, integration, or workspace configuration are not saved, the cause may involve validation requirements, insufficient permissions, session problems, or temporary processing errors. Follow these steps to identify the issue. 1. Check for validation messages. Review the form for missing required fields, invalid values, or configuration conflicts. 2. Confirm that you have permission to edit the resource. Some settings may only be available to users with specific administrative or operational roles. 3. Review your connection. An interrupted network request can prevent changes from reaching the platform. 4. Check your session. If your authentication session has expired, the save operation may fail or require you to sign in again. 5. Avoid multiple simultaneous edits. If several people are changing the same configuration, coordinate the changes to reduce the risk of confusion or unintended overwrites. 6. Save a small, controlled change. Where appropriate, test whether a minor valid modification can be saved. 7. Reload and verify. After receiving confirmation that a change was saved, reload the relevant page and check whether the expected value remains. 8. Review dependent configuration. Some settings may require valid references, permissions, or related resources. If the save operation fails, inspect any available error message. What if the interface reports success but the old value returns? This may indicate a display issue, a conflicting update, or a problem persisting the change. Record the exact sequence of actions and contact Support. Should I keep clicking Save? Avoid repeated submissions if the operation appears to be processing. Wait for a result and verify the current state before trying again. When to contact Support Provide the affected configuration page, approximate time, expected change, actual result, and exact error message if one appears. Do not share credentials, API keys, or sensitive business information unnecessarily. If the issue affects an active business-critical workflow, avoid making further configuration changes until the current state is understood.