Start by identifying the specific action that failed. “A file upload failed” or “an automation did not start” is more useful than “Aleria is not working,” and helps you check the right part of the product.
Check the basics
- Confirm the account and organization you are using.
- Read the error shown on the page or in the conversation.
- Check access to the project, file, app, or external account involved.
- For connected services, inspect the connection in Plugins.
- For recurring work, inspect the automation's state and run history.
Before retrying an action that sends a message or creates a record, check whether it already completed in the destination service.
Use the focused guides
See file troubleshooting, plugin troubleshooting, automation runs, or account and sign-in.
Contact support
Email support@aleria.com with the action you attempted, what you expected, what happened, the time and timezone, and the error text. Include your app or browser version and a relevant conversation or item link if appropriate.
A screenshot can help, but remove information unrelated to the problem. Do not include passwords, one-time codes, access tokens, or API keys. If source files are needed, ask for the appropriate way to provide them.
For organization membership, plan restrictions, or identity-provider approval, your administrator may be the quickest first contact.