What is Konnector history?

Konnector History in Konnectify refers to the log of all past Konnector runs, showing details about when and how each automation was executed. It helps users track successful task executions, troubleshoot errors, and analyze automation performance.

How to Access Konnector History:

STEP 1: Click on the “Konnector History” icon in the toolbar on the left side of the window.

STEP 2: This will be your Konnector History, where you can view logs, filter results, and troubleshoot issues.

• Konnector History is useful for monitoring automation efficiency and ensuring smooth workflows.

• You can filter results based on execution status, date, or specific Konnectors.

• Each entry includes key details such as:
  
  

• Status – Whether the automation was successful, failed, or partially successful.

• Execution Time – When the Konnector was triggered.

• Task executed _ Number of tasks completed.

Understanding Konnector Statuses

Each Konnector execution is assigned one of the following statuses:

You can filter the Konnector Statuses, using the filter option available.

Success

• The Konnector ran successfully with no errors.
  
  

• All tasks were executed as expected, and data was processed correctly.
  
  

• No further action is required.
  
  

Warning

• The Konnector executed but encountered minor issues.
  
  

• Some non-critical errors occurred, but the main workflow continued.
  
  

• Example: A field was missing, but the Konnector still processed the available data.
  
  

• Users should review the warning details and make necessary adjustments.
  
  

Failure

• The Konnector could not execute due to a critical error.
  
  

• Common causes of failure:
  
  

  • Authentication issues (expired API keys or incorrect credentials).
    
    

  • Invalid input data (missing required fields).
    
    

  • Connection errors (network issues or app downtime).
    
    

  • Incorrect workflow setup (misconfigured triggers or actions).
    
    

• Click on the error message in the log to view details and troubleshoot.
  
  

No Input

• The Konnector was triggered but found no data to process.
  
  

• This can happen if:
  
  

  • The source app had no new data to process.
    
    

  • The applied filters were too restrictive.
    
    

  • The Konnector was set up incorrectly.
    
    

• Users should check the input source and filters to ensure correct data flow.
  
  

Partial Success

• Some parts of the workflow ran successfully, while others failed.
  
  

• Possible reasons:
  
  

  • A step in the automation had an error, but previous steps worked.
    
    

  • A third-party app (e.g., Gmail, Slack) had temporary issues.
    
    

  • Some data was processed, but not all due to validation issues.
    
    

• Users should review the error log, retry failed steps, or reconfigure the workflow.

For further assistance, contact Konnectify’s support team.