Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spojit.com/llms.txt

Use this file to discover all available pages before exploring further.

The monitoring view gives you visibility into every workflow execution — past and present.

Execution history

Navigate to the Executions page from the sidebar to see a list of all workflow runs across your workspace. Each entry shows:
ColumnDescription
WorkflowThe workflow name
StatusCompleted, Failed, Running, or Waiting
StartedWhen the execution began
DurationTotal execution time
TriggerHow it was triggered (manual, schedule, webhook)

Execution detail

Click on an execution to see the step-by-step breakdown:

Step timeline

Each node in the workflow is shown with its:
  • Status — whether it succeeded, failed, or was skipped
  • Duration — how long the step took
  • Input — the data the node received
  • Output — the data the node produced

Error details

When a node fails, the execution detail shows:
  • The error message
  • The input data that caused the failure
  • The specific node where the failure occurred
Filter the execution list by:
  • Workflow — show runs for a specific workflow
  • Status — filter by completed, failed, or running
  • Date range — narrow down to a specific time period

Debugging tips

Open the execution detail and click the failed node. Check the Input data to make sure it matches what the tool expects. Common issues include missing required fields, wrong data types, or expired credentials.
Click through each node to inspect the Output at every step. Find the node where the data diverges from what you expected, and check its configuration.
This usually means a node is waiting for an external response (e.g., a slow API) or the workflow hit a timeout. Check if a Human approval node is waiting for action.
Verify the webhook URL is correct and the external service is sending a POST request with a JSON body. Check the execution history — if no entries appear, the request may not be reaching Spojit.

Re-running a workflow

From the execution detail, you can re-run the same workflow with the original inputs to test a fix. This is useful after updating a node’s configuration or fixing a credential issue.