Automation Rule Logging for Collaborative Workflow Troubleshooting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current project management software lacks efficient tools for automating changes across third-party applications and troubleshooting automation tasks, particularly in complex collaborative work systems where hundreds of automations operate simultaneously, leading to challenges in identifying logical errors.

Innovation Solution

A system that maintains a table with rows and columns in a primary application, enabling the construction of automations defined by conditional rules to alter internal and external information, monitors specific cells for information input, and triggers functionality in third-party applications, while also providing mechanisms to troubleshoot faulty automations by recording actions and identifying recent logical rule activities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple automations are implemented in collaborative work systems, then productivity is improved through automation of tasks, but device complexity increases making troubleshooting difficult

Engineering Contradiction:
Improveautomation efficiencyVSAvoidautomation system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the complex automation system into individual automation instances, each with unique identifiers. This allows the system to divide the troubleshooting task into manageable parts by examining one automation at a time rather than attempting to analyze all automations simultaneously, thus reducing the perceived complexity while maintaining high productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms that provide real-time information about automation execution status, errors, and performance metrics. This feedback loop enables automatic detection and reporting of issues without manual intervention, allowing the system to maintain high automation levels while reducing the complexity of troubleshooting through automated monitoring and diagnostic capabilities.

Inventive Principle:
Principle #23Feedback

2Reliability

If comprehensive automation monitoring is implemented, then reliability of automation execution is improved, but loss of time increases due to monitoring overhead

Engineering Contradiction:
Improveautomation execution reliabilityVSAvoidmonitoring time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies partial monitoring by focusing only on critical automation execution points and error-prone operations rather than monitoring every aspect of automation execution. This selective approach maintains high reliability for critical functions while reducing the time overhead associated with comprehensive monitoring of all automation activities.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system replaces manual monitoring and troubleshooting mechanisms with automated electronic monitoring systems that use sensors, event loggers, and diagnostic tools to automatically detect and report automation issues. This substitution eliminates the need for human operators to spend time manually monitoring automation execution while maintaining or improving reliability through continuous automated surveillance.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11475408B2Digital processing systems and methods for automation troubleshooting tool in collaborative work systems
Publication Date: 2022.10.18 MONDAY COM LTD
  • US11475408B2 patent drawing
  • US11475408B2 patent drawing
  • US11475408B2 patent drawing

AI summary

Systems and methods for troubleshooting faulty automations in tablature. A system may include at least one processor configured to maintain a table containing data, store a plurality of logical sentence structures that serve as logical rules to conditionally act on the data in the table, wherein each logical rule is enabled to act at differing times in response to differing conditional changes, activate the logical rules so that each rule is in effect simultaneously, as each logical rule performs an action on the data, record the action and an associated time stamp in an activity log. The processor may access the activity log to identify at least one most recent action performed on the table, and present at least one specific logical sentence structure underlying at least one logical rule that caused the at least one most recent action.