
In my role as a Business Systems Analyst, I use SmartSuite to manage Reports. It gives staff a structured way to submit incident details and lets our team organize and track reports by date, building, incident type, and status. The record fields and activity history help me understand the workflow, review how reports move through the process, and discuss requirements or issues with AppDev. Having the report information centralized makes the process easier to follow. Review collected by and hosted on G2.com.
In our workflow, some submitted incident reports remained queued instead of appearing in the scheduled summary email. It takes extra effort to find where the process stopped and whether the issue is in SmartSuite or the connected email workflow. A clearer activity log showing automation attempts, selected or skipped records, delivery status, and errors would make troubleshooting faster. Review collected by and hosted on G2.com.
Thank you, Isha. I am glad the Duty Report process has one structured place to live. On reports that stayed queued: each automation has a History tab listing every run, its status and each action's error, and a record's activity history links to the run that changed it. A per-run view of which records were selected or skipped is a fair ask; I have passed it to our product team. Jon Darbyshire, CEO
https://help.smartsuite.com/en/articles/7115398-automation-run-history-erroring
https://help.smartsuite.com/en/articles/17730207-fix-an-automation-that-did-not-run