How can we help?

If an expected notification does not appear, the first step is to determine whether the underlying event occurred and whether that event is supported by the relevant notification mechanism. Not every operational event automatically generates a notification. The available behavior depends on the module, account configuration, and implemented delivery capabilities. Step 1: Confirm that the event occurred Open the module associated with the expected notification. For example, if the event relates to an automation or business process, review its execution history. Check whether the relevant activity actually ran and whether the expected result or failure was recorded. Step 2: Verify notification support Determine whether the specific event is intended to generate a notification. Do not assume that every status change, execution, or error produces an alert. Step 3: Check the correct account and workspace Confirm that you are signed in to the appropriate Polyosync account. If you have access to multiple operational environments, verify that you are reviewing the correct one. Step 4: Review your permissions Some operational information may be restricted according to user roles or module access. If you cannot view the relevant activity, contact the appropriate workspace administrator. Step 5: Refresh the relevant interface If the event is expected to appear in the application, refresh the page and review the notification area again. A temporary interface or network issue may prevent recently updated information from appearing immediately. Step 6: Check the intended delivery channel If you expect an email, browser notification, or mobile push notification, first confirm that the channel is supported for that event. Where applicable, check the relevant permissions and delivery settings. Step 7: Investigate related errors If the underlying operation failed, review its execution details. An execution failure and a notification delivery issue are different problems and may require separate investigation. Step 8: Contact Polyosync Support If a supported notification is still missing, provide: 1. The affected module. 2. The event you expected to generate a notification. 3. The approximate date and time. 4. The account role involved. 5. The delivery channel you expected. 6. Any relevant non-sensitive execution or error information. Do not include passwords, access tokens, API keys, or unnecessary customer data. Can notifications be delayed? Delivery and interface updates may be affected by the relevant implementation and temporary service conditions. Users should verify the underlying event independently when timing is important. What if the notification is business-critical? Do not rely exclusively on an unverified notification mechanism. Review the relevant execution records and use established operational procedures until notification delivery has been confirmed. The recommended approach is to investigate the event, the notification mechanism, and the recipient's access separately. This makes it easier to identify the actual cause.