Lifecycle & Support

Lifecycle & Support

• Versioning & lifecycles → Updates, maintenance, and deprecation.

• Troubleshooting → Fixing blockers like permissions or missing connections.

---

Versioning & Lifecycles

AI Employees are updated and maintained like other system components in Motion. This section defines how they evolve over time and what users can expect when versions change.

Feature	Details
Version updates	AI Employees receive updates that may include new skills, improved models, or adjusted defaults. Updates are rolled out progressively across workspaces.
Backward compatibility	Existing skills and configurations are preserved during version updates whenever possible. Some updates may change outputs or behavior.
Visibility of changes	Major updates are announced in release notes. Changes are reflected in the AI Employee’s behavior and available skill set.
Custom configurations	User-created skills remain intact through updates but may require adjustments if dependent integrations change.
Recovery	If an AI Employee is retired, dependent workflows may fail. Users should migrate to a replacement employee or update workflows before end of lifecycle.

Troubleshooting

AI Employees may encounter blockers when running skills or integrations. Common issues and their resolutions are listed below.

Issue	Cause	Fix
“Permission denied” error	The AI Employee’s role (Viewer, Editor, Admin) does not allow the requested action.	Check the workspace RBAC settings. Upgrade the AI Employee’s role if the action requires higher permissions.
Skill fails with external service	The required integration (e.g., Google Calendar, Slack) is not connected or has expired.	Reconnect the integration under Settings → Integrations.
Action blocked for approval	The AI Employee attempted a write operation that requires explicit approval.	Approve the action in chat or adjust approval settings in workspace configuration.
Employee not responding in chat	The AI Employee is disabled or removed from the workspace.	Verify the AI Employee is enabled under workspace members. Re-add if necessary.
Autonomous skill not running	The skill trigger is misconfigured or outside of scope (e.g., no matching events).	Review the skill configuration, triggers, and workspace context.
Output missing from project or doc	The action was declined, deleted, or the connection failed mid-run.	Re-run the skill and verify connections are active.