Status: Resolved AI service Routing is working as expected and all AI services are back to normal. Affected components
 <ul>
 <li>ABBYY (Operational)</li>
 </ul>

Degraded Performance - AI Service Routing

Status: Complete Maintenance has completed Affected components
 <ul>
 <li>Integrations (Under maintenance)</li>
 </ul>

Maintenance: Activepieces Platform Upgrade

Maintenance: Activepieces Internal Network Optimization

Status: Scheduled Integrations application

What's changing

We are updating how job concurrency limits are calculated for automation integrations. Currently, the limit is applied per pipe. Going forward, it will be applied per organization, with a cap of 50 simultaneous jobs per organization, regardless of the number of pipes within that organization.
This means that jobs across all pipes in your organization will now share a single concurrency quota at the organization level.

Previous limit:

10 jobs / Pipe
New limit
50 jobs / org

Who is affected

Organizations with multiple pipes — your concurrent job allowance is now shared across all pipes in your org, up to 50 at once.
Daily automation usage — not affected. This change only impacts burst scenarios where more than 50 jobs are triggered simultaneously.
Why we're making this change
This update ensures fairer resource distribution across all customers and improves queue processing stability for everyone — especially during peak usage periods. Large bursts of simultaneous jobs from a single organization will no longer be able to delay processing for other customers.
The new per-organization concurrency limit is already documented in our Integrations Limits help article.

What you should do

No action is required for most customers. If your workflows rely on firing large batches of jobs simultaneously (more than 50 at once), we recommend reviewing your automation triggers before the change takes effect to avoid unexpected queuing delays.
If you have questions, please reach out to our support team.

When will this change occur

This change takes effect 30 days from the date of this notice.
Scheduled to 2026 August 6 

Start time

August 6, 2026 — 09:00 BRT

Expected end

August 6, 2026 — 10:00 BRT

Duration

~60 minutes Affected components
 <ul>
 <li>Integrations (Under maintenance)</li>
 </ul>

Maintenance: Update to job concurrency, Integrations Ipass limits

Status: Resolved The incident was resolved Affected components
 <ul>
 <li>Application (Operational)</li>
 </ul>

Cards are not opening due to the missing "from_name"

Pipefy Core Slowness

Status: Complete Maintenance has completed Affected components
 <ul>
 <li>Authentication (Under maintenance)</li>
 </ul>

Maintenance: Scheduled maintenance — infrastructure security upgrade

Maintenance: Emergency Scheduled Maintenance — Integration Platform (iPaaS)

Pipefy slowness

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Integrations (Operational)</li>
 </ul>

Integrations downtime

Status: Resolved A fix was applied, and the incident was resolved. Affected components
 <ul>
 <li>Public Form (Operational)</li>
 </ul>

The embedded start form iframe is not working

Status: Complete The scheduled maintenance has been completed.

Maintenance: OCI Cloud Provider Maintenance

Status: Resolved Root Cause

The issue was caused by an automation process that affected the system's performance. During this time, the speed of processing tasks was slower than usual, impacting the overall efficiency.

Resolution

The problematic automation was removed, which restored the system's performance back to its normal state, ensuring that operations could continue smoothly.

Automations Slowness

Status: Resolved This incident has been resolved. Affected components
 <ul>
 <li>Filters (Operational)</li>
 </ul>

Search and filters Slowness

Maintenance: Emergency OCI Provider Maintenance

Maintenance: Mandatory Infrastructure upgrade — Cache System

Status: Resolved Root Cause

The issue was traced back to a firmware update in a database instance, which led to a failure in the system's ability to switch over to a backup. This caused the main application to go down.

Resolution

The problem was resolved by starting the database on a new healthy instance, restoring the system's functionality.

Action Plan

• To prevent future occurrences, a manual switch-over will be performed before any instance restarts.
• Additionally, a maintenance is scheduled for the system update to address the identified bug.

Application is down

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>Activities (Operational)</li>
 </ul>

Maintenance: Activities database maintenance

Status: Resolved Root Cause

The application experienced performance issues due to a spike in executing flows that affected the app's performance. During the investigation, an issue was identified, requiring a fix to resolve the problem permanently.

Resolution

A fix to address the issue was implemented in the application, ensuring the application's performance returned to normal.

Action Plan

The team will monitor new metrics in the scenario, to avoid the future impact

Integrations slowness

Status: Resolved This incident was resolved after a fix being implemented Affected components
 <ul>
 <li>Integrations (Operational)</li>
 </ul>

(Integrations) Flow executions are experiencing delay on processing time

Status: Complete The scheduled maintenance has been completed. Affected components
 <ul>
 <li>Automation (Operational)</li>
 </ul>

Is Pipefy down?

Pipefy status is UP

Lastest published events

Degraded Performance - AI Service Routing

Maintenance: Activepieces Platform Upgrade

Maintenance: Activepieces Internal Network Optimization

Pipefy Services, Components and Regions

Recent Pipefy events

Degraded Performance - AI Service Routing

Maintenance: Activepieces Platform Upgrade

Maintenance: Activepieces Internal Network Optimization

Maintenance: Update to job concurrency, Integrations Ipass limits

Cards are not opening due to the missing "from_name"

Pipefy Core Slowness

Get your FREE account now,
5 monitors included!

Is Pipefy down?

Pipefy status is UP

Lastest published events

Degraded Performance - AI Service Routing

Maintenance: Activepieces Platform Upgrade

Maintenance: Activepieces Internal Network Optimization

Pipefy Services, Components and Regions

Recent Pipefy events

Degraded Performance - AI Service Routing

Maintenance: Activepieces Platform Upgrade

Maintenance: Activepieces Internal Network Optimization

Maintenance: Update to job concurrency, Integrations Ipass limits

Cards are not opening due to the missing "from_name"

Pipefy Core Slowness

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!