Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.refold.ai/llms.txt

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

There are various types of Logs that you can see in Refold:

Execution Logs

Execution Logs is able to provide various details about a workflow that was executed. With features such as detailed execution details and request/response data, workflow logs enable users to gain deeper insights into the execution process and ensure optimal performance. To view the Logs, navigate to Logs in Refold and check the Executions tab.
You can even filter out the logs based on Workflow name, Status, Linked Account etc.
Workflow Logs Refold Key Functionalities To test a workflow in Refold, user can also execute a workflow through the Try API section in Refold.
To learn more about Try API and how it can be used, refer to our guide here.
Some of the key functionalities of Workflow logs are described in details below:

Logs Views

For your Execution Logs, you can also create your own Custom Views with a set of filters already applied to it.To create a View, click on +New View button in the top right corner of Execution Logs screen.Views of Workflow logs in RefoldNow apply any filter that you want and click on Save in the top right corner.

Node Activity Details

By clicking on a workflow log, users can view the activity of individual nodes present in the workflow.This includes information about the status or errors encountered by each node, response etc. providing insights into the execution flow and potential points of failure.Execution details of Workflow nodes in Refold

Replay & Retry Functionality

For workflows that encounter errors, users have the option to retry complete execution by clicking on the Replay button in the top right corner or individually running an errored node again by clicking on Retry.
The Replay functionality is limited to a single attempt.
Retry an errored Workflow in Refold

Event Logs

Event logs in Refold provide information about the triggers and events called.
To learn more about Event in Refold, refer to our guide here.
To access the Event Logs, navigate to the Logs section in Refold and select the Events tab.
You can filter the logs based on Event name, Status and Linked Account ID etc.
Event Logs Refold Each Event Log entry provides you information about the Workflows that got executed on Event call, the Event URL and the Payload that was sent in the event.
The Workflows section will not be visible if there was no Workflow that was associated with the event.
Details of an Event in Refold

Webhook Logs

Webhook logs allows users to monitor the execution of webhooks subscribed to in Refold. Webhook logs provide detailed information about each webhook event, including its Execution status, Linked Account ID, fired date and more. To access the Webhook Logs, navigate to the Logs section in Refold and select the Webhooks tab. Webhook Logs Refold
To learn more about Webhooks in Refold and how they can be subscribed, refer to our guide here.
For each webhook event, users can view the associated request and response data, providing insights into the interaction between Refold and external systems. Details of a Webhook in Refold

Schedule Logs

Schedule Logs provide users with visibility into scheduled workflows and their associated details. To access the Schedule Logs, navigate to the Logs section in Refold and select the Schedules tab. Schedule Logs Refold In Refold, Schedule Logs offer a comprehensive view of scheduled workflows, displaying essential information such as:

Workflow Name and ID

Identifies the workflow scheduled for execution.

Schedule Cron

Specifies the cron expression defining the schedule for workflow execution.

Event

Indicates the Event ID triggering the scheduled workflow.

Status

Reflects the current status of the scheduled workflow, either Active or Inactive.
These details enable users to quickly identify scheduled workflows, understand their configurations, and track their status within the Refold platform.