How can we help?

Reporting issues can arise for different reasons, including missing source data, incorrect assumptions about metric definitions, access restrictions, or problems affecting the relevant operational module. The most effective troubleshooting approach is to identify whether the issue concerns the underlying activity, the available reporting functionality, or the interpretation of the data. Problem 1: I cannot find the report I need. First, verify that the reporting feature is available for your account. Check the relevant operational module for execution history or activity information. Not every type of business analysis is necessarily available through a consolidated reporting interface. Problem 2: An execution does not appear in the expected information. Verify that the operation actually ran. Review the relevant automation, workflow, or business process execution history. Check whether the activity was recorded and whether the expected reporting view includes that type of record. Problem 3: The report contains fewer activities than expected. Confirm the reporting period and the definition of the metric. Determine whether the measurement includes all attempted executions or only particular execution statuses. Review whether the underlying records are complete. Problem 4: The report contains more activities than expected. Check whether repeated runs, retries, or separate operational events are being counted. Do not assume that every execution corresponds to a unique customer request or completed business outcome. Problem 5: An execution is marked successful, but the business result is incorrect. Review the execution result and the underlying business requirements. A technically successful operation may still produce an outcome that requires correction. Problem 6: The information differs between modules. Different modules may record different aspects of the same business activity. Verify that you are comparing equivalent measurements and periods. Problem 7: Financial calculations do not match business records. Review the calculation method and the underlying financial data. Check whether estimates have been mixed with confirmed revenue or expenses. Verify that benefits and costs have not been counted more than once. Problem 8: I cannot access the reporting information. Confirm that you are using the correct workspace. Review your role and permissions with the appropriate administrator. Also verify that the relevant feature is available in your account. Problem 9: Reporting information appears outdated. Check whether the underlying activity has been recorded. Refresh the relevant interface where appropriate. If the information depends on an external system, verify that the source data is current. Do not assume that every report or operational view updates instantaneously. Problem 10: I cannot determine why a metric changed. Compare the relevant periods and investigate the underlying execution records. Look for changes in workload, configuration, dependencies, or operational conditions. Avoid attributing changes to a single cause without supporting evidence. What information should I provide when contacting support? Include: 1. The affected Polyosync module. 2. The report or metric involved. 3. The relevant date range. 4. The expected behavior or value. 5. The actual behavior or value. 6. Any relevant non-sensitive execution identifiers. 7. The steps needed to reproduce the issue, where applicable. Do not include passwords, API keys, access tokens, or unnecessary personal information. How can I prevent recurring reporting problems? Use consistent metric definitions. Verify the underlying source records. Document financial assumptions. Review permissions periodically. Investigate discrepancies before relying on the results. Final recommendation Treat reports as an interpretation of operational evidence, not as a substitute for that evidence. When a report appears incorrect, begin by verifying the relevant execution records and the definition of the measurement. This approach helps businesses distinguish actual operational problems from reporting or interpretation issues.