Troubleshooting tips
Problem description | Solution |
---|---|
This component does not send any email messages. | Make sure that the Account settings are correct, and that the recipient’s email address is correct. If you have multiple recipients, make sure that their addresses are separated by the semicolon character (;). |
When the component tries to send messages and the following error appears: "Unable to route Knowledge Object (One or more errors occurred. Code: ResourceNotFound Message: Resource could not be discovered…)" |
This error appears when the From field references a non-existing Microsoft 365 organizational mailbox. To solve this problem, check the From field setting on the Mail settings tab. |
When the component tries to send messages and the following error appears: "Unable to route Knowledge Object (One or more errors occurred. Code: ErrorSendAsDenied" "Message: The user account which was used to submit this request does not have the right to send mail on behalf of the specified sending account., Cannot submit message.…)" |
This error appears when the user account template string is resolved, but the user has no permission to send on behalf of the sender in the From field. To solve this problem, check the From field setting on the Mail settings tab and/or grant the necessary permissions. |
The component displays the error message: "One or more errors occurred. Object reference not set to an instance of an object." |
By default, the component displays a general error message: "One or more errors occurred. Object reference not set to an instance of an object." To obtain more detailed error messages from the Graph API, enable the Extended Logging in the MS Graph section in the configuration file by changing the EXTENDED LOGGING value to "ON" (it is "OFF" by default). The configuration file should not be active in AutoStore during this process; stop the AutoStore service and close the AutoStore Process Designer to ensure the configuration is not loaded while modifying. Extended Logging should be ON only while producing logs to narrow down where the issue is; it should be OFF for production use. Example: AutoStore.Components.MsGraphRoute.Mail.MsGraphMailRoute{ ... TIMEOUT = 100 EXTENDED LOGGING = ON ... } |
The component does not send attachments larger than 4 MB | Microsoft Graph API's mail.send endpoint has a distinction in file upload sizes when sending email attachments. By default, individual attachments are limited to 4 MB if uploaded directly via the API. Larger attachments, with sizes up to 150 MB, utilize the upload session method, allowing them to be uploaded in chunks. To set up firewall rules, do the following: 1. Allow access to the primary Microsoft Graph API endpoint: Ensure that your firewall rules allow outbound traffic to the Microsoft Graph API endpoints. The primary Graph API endpoint is: https://graph.microsoft.com/ 2. Allow upload session-specific URLs: When creating an upload session, Microsoft Graph provides a specific endpoint for the upload process. This endpoint is a temporary URL with a unique domain (like outlook.office.com or other Office 365-specific domains). Make sure to allow these dynamically generated URLs by whitelisting the relevant Microsoft 365 domains. Microsoft publishes an IP and URL list for Office 365 and related services that can help configure these rules. 3. Allow HTTPS traffic: Ensure that port 443 (HTTPS) is open for outbound connections, as all Graph API and upload sessions occur over HTTPS. 4. Configure idle and session timeouts: Large file uploads in chunks may take longer to complete, so firewall timeouts may need adjustment to accommodate the duration of these uploads, especially for files close to the 150 MB limit. 5. Regular updates for Microsoft IP ranges: Microsoft’s IP ranges for Office 365 and Graph API services may change periodically. Make sure to update your firewall rules according to the latest IP ranges and domains from Microsoft's official documentation. |