Source

Execution, error handling & monitoring — found from sitemap — Pipefy

Checked for Pipefy on 13 Oct 2026

Page: http://help.pipefy.com/en/articles/15275092-understanding-the-integration-queue-status-and-flow-runs
Checked: 13 Oct 2026, 17:26 UTC
How we may use it: Public page, crawling permitted

Technical details

type: page
http status: 200
content hash: sha256:5d053f48db0efb9df73e3a0e08a642873645cdf8438fa0cfaf310fa5ba4995b8
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Run id creation Report an error

“Every time a Pipefy integration flow is triggered by an event, the system automatically creates a unique Run ID (acting as a digital receipt or Job ID for that specific execution).”
Async processing Report an error

“Pipefy handles these runs via asynchronous processing. This means the system acknowledges the trigger instantly”
Queue ordering Report an error

“Queued runs are held safely in a centralized waiting line and will automatically execute in a strict order of arrival the moment your active concurrent slots drop below 50.”
Queue status widget Report an error

“On the top right corner of the Runs dashboard, you will find the new interactive Queue Status widget.”
Queue widget metrics Report an error

“Total Runs: The total volume of unique flow runs currently handled within the monitoring view.”
Failed run definition Report an error

“Failed (Red bar): The number of flow runs that stopped due to structural errors, data payload issues, or an execution that breached governance boundaries.”
No data loss in queue Report an error

“ensuring that no data is ever dropped when volume spikes occur.”
Pagination recommendation Report an error

“If your business needs to process large datasets without stacking runs into the waiting queue, we recommend utilizing pagination and small delays.”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.