# FAQ & Troubleshooting

# FAQ & Troubleshooting

This section provides answers to frequently asked questions about Automated Workflow and its functionalities within Purple Fabric.

1. ** What is the difference between an Agent, Team of Agents and an Automated Workflow? ** An Agent is a focused component designed to perform a specific intelligent task (e.g., classification or summarization). An Automated Workflow, on the other hand, is a multi-step orchestration that combines agents, tools, logic, and external systems to complete an end-to-end business process.

   Unlike a Team of Agents, which intelligently works multiple agents to achieve a goal collaboratively, an Automated Workflow executes agents and components sequentially and deterministically based on predefined business logic.

2. **How do I handle potential errors within a specific component? ** You can use an If/Else component to check the status or output of a preceding component. If an error is detected , you can direct the flow down a specific error-handling path, such as sending a notification or logging the issue to a database.

3. **Can I reuse a component or logic across multiple workflows? ** While workflows themselves are self-contained, you can replicate logic by exporting a workflow as a JSON file and importing it into another workflow. This enables reuse of complex flows like input validation, document routing, or error handling.

4. **Why can’t I see transactions in the Asset Monitor after running a workflow? ** Your workflow might be inactive or unpublished. Go to the Governance tab and ensure the status is set to Active. Also verify that the trigger is properly configured.

5. **Why is my Agent not appearing in the Automated Workflow? ** This typically happens when the asset was not successfully created or lacks the correct visibility settings. Double-check the asset creation step and ensure you have access to the relevant workspace and permissions.

6. **Why is the Variable Assigner component empty or showing no fields? ** The Variable Assigner component is used to modify existing Environment Variables during a workflow's execution. If you have not created any Environment Variables in the workflow's Settings tab first, the "Label" dropdown in the component's configuration panel will be empty. You must define an Environment Variable before you can assign a value to it.

   **My workflow is failing with a "Connection Failed" error. What could be wrong? ** Check the following:

   1. Credentials: Navigate to the central Accounts section and test the connection for the relevant service. Ensure the credentials are correct and have not expired.

   2. Permissions: Confirm that the account associated with the credential has the required permissions in the third-party application

   3. Network Access: Ensure that the platform has network access to the target system's endpoint and is not being blocked by a firewall

7. **Data is not being passed correctly between two components. How can I debug this? ** This usually indicates an incorrect data mapping. To resolve it:

   1. Run a Test and inspect the Output of the source component to see the exact structure of the data it is producing.

   2. Inspect the Input of the destination component to see what it received.

   3. Open the destination component's Configuration Panel and verify that the mapping is pointing to the correct output variable from the source component.

8. **A validation error is blocking me from publishing my workflow. What should I do? ** The system will highlight the exact component that is misconfigured. Check for these common issues:

   1. A required input field in the component is not mapped.

   2. A selected Connection is invalid or has been deleted.

   3. The component is not linked to any other part of the flow.

9. **My Event-Driven Trigger is not starting the workflow. Why? ** Ensure the following are correct:

   1. Source Event: Confirm that the event (e.g., a new email arriving, a new file being uploaded) is actually happening in the external system.

   2. Trigger Configuration: Re-open the Start node and verify that all connection details (e.g., folder path) are accurate.

   3. Activation Status: Go to the Governance tab and ensure the workflow's status is "Active." An "Inactive" workflow will not be triggered