Enable or Disable Prompts

While working on your app, you may encounter situations where you want to temporarily disable a prompt without removing it entirely. Disabling a prompt prevents it from being executed during the workflow, allowing you to test or refine other parts of the app. Similarly, you can re-enable a previously disabled prompt if you decide to include it back into the workflow.

Steps to Disable a Prompt:

1. Open the App Editor
   Navigate to the Prompts section where all your prompts are listed.

2. Locate the Prompt You Want to Disable
   Identify the prompt(s) that you no longer want to execute but do not wish to delete.

3. Disable the Prompt

   • Click on checkbox of the prompt(s) to open its options header.
   • Look for the Enable/Disable dropdown menu or "power button" icon.
   • Select the Disable option.
   • Alternatively, locate the "power button" icon on the right-end of the specific prompt, and click to disable it.
   • Scroll to the bottom of the prompts and click Save.
   • Once disabled, the prompt will remain in the workflow but will be skipped during execution.
   
   

Steps to Enable a Disabled Prompt:

1. Access Your App Editor
   Follow the same steps to open the Prompts area where the disabled prompt is located.

2. Identify the Disabled Prompt
   Disabled prompts are have a grayed "power button" icon to indicate it as being disabled.

3. Enable the Prompt

   • Click the checkbox on the disabled prompt(s).
   • Click the "power button" icon dropdown menu, and select Enable to turn on the prompt(s).
   • Scroll to the bottom of the prompts and click Save.
   • The prompt will now be reactivated and included in the workflow during execution.
   
   

Why Disable Instead of Delete?

• Flexibility for Testing: Temporarily disabling a prompt allows you to test alternative workflows without losing the original setup.
• Easier Troubleshooting: When debugging or refining workflows, disabling prompts helps isolate and identify potential issues.
• Reusability: A disabled prompt can be quickly re-enabled, saving time compared to recreating it from scratch.

Important Notes:

• Disabled prompts do not consume credits or API usage while inactive.
• Disabling a critical prompt may cause errors or unexpected behavior if subsequent prompts rely on its output.
• Always review your workflow after re-enabling prompts to ensure everything functions as expected.