You can control workflow-specific settings in your workflow's Settings:
- Visit your workflow
- Select the ... menu at the top-right and click Settings:
[[toc]]
If you'd like to pause your workflow from executing completely, you can disable it or reenable it here.
By default, you'll receive notifications when your workflow throws an unhandled error. See the error docs for more detail on these notifications.
You can disable these notifications for your workflow by disabling the Notify me on errors toggle:
Workflows have a default execution limit, which defines the time workflows can run for a single invocation until they're timed out.
If your workflow times out, and needs to run for longer than the default limit, you can change that limit here.
By default, workflows run with {{$site.themeConfig.MEMORY_LIMIT}} of memory. If you're processing a lot of data in memory, you might need to raise that limit. Here, you can increase the memory of your workflow up to {{$site.themeConfig.MEMORY_ABSOLUTE_LIMIT}}.
Pipedream charges invocations proportional to your memory configuration. When you modify your memory settings, Pipedream will show you the number of invocations you'll be charged per execution. Read more here.
Manage the concurrency and rate at which events from a source trigger your workflow code.
Sometimes, you'll need to reference static files in your workflow, like a CSV. Files uploaded in the Attachments section can be referenced in your workflow under the steps.trigger.context.attachments object.
For example, if you upload a file named test.csv, Pipedream will expose the file path of the uploaded file at steps.trigger.context.attachments["test.csv"]. You can read the contents of the file using fs.readFileSync:
import fs from "fs";
const fileData = fs.readFileSync(steps.trigger.context.attachments["test.csv"]).toString();
console.log(fileData);
Each attachment is limited to 10MB in size. The total size of all attachments within a single workflow cannot exceed 200MB.