You can control workflow-specific settings in your workflow's Settings:
- Visit your workflow
- Select the ... menu at the top-right and click Settings:
# Enable Workflow
If you'd like to pause your workflow from executing completely, you can disable it or reenable it here.
# Error Handling
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:
# Auto-retry Errors
Customers on the Advanced Plan (opens new window) can automatically retry workflows on errors. If any step in your workflow throws an error, Pipedream will retry the workflow from that failed step, re-rerunning the step up to 8 times over a 10 hour span with an exponential backoff (opens new window) strategy.
On error, the step will export a
$summary property that tells you how many times the step has been retried, and an
$attempt object with the following properties:
error— All the details of the error the step threw — the error, the stack, etc.
cancel_url— You can call this URL to cancel the retry
rerun_url— You can call this URL to proceed with the execution immediately
resume_ts— An ISO 8601 timestamp that tells you the timestamp of the next retry
If the step execution succeeds during any retry, the execution will proceed to the next step of the workflow.
If the step fails on all 8 retries and throws a final error, you'll receive an error notification through your standard notification channel.
# Send error notifications on the first error
By default, if a step fails on all 8 retries, and throws a final error, you'll receive an error notification through your standard notification channel. But sometimes you need to investigate errors as soon as they happen. If you're connecting to your database, and receive an error that the DB is down, you may want to investigate that immediately.
On any workflow with auto-retry enabled, you can optionally choose to Send notification on first error. This is disabled by default so you don't get emails for transient errors, but you can enable for critical workflows where you want visibility into all errors.
For custom control over error handling, you can implement error logic in code steps (e.g.
catch statements in Node.js code), or create your own custom error workflow.
# Execution Controls
# Execution Timeout Limit
Workflows have a default execution limit, which defines the time the workflow can run for a single execution until it's 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
256MB 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
Pipedream charges credits proportional to your memory configuration. When you modify your memory settings, Pipedream will show you the number of credits you'll be charged per execution. Read more here.
# Concurrency and Throttling
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
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
import fs from "fs"; const fileData = fs .readFileSync(steps.trigger.context.attachments["test.csv"]) .toString(); console.log(fileData);
Each attachment is limited to
25MB in size. The total size of all attachments within a single workflow cannot exceed