Resolved after 12 minutes, affecting Filters, on January 9, 2026.
**Root Cause** The issue was caused by a non-optimized query that struggled when handling more than 50 records, leading to problems in database searches. **Resolution** The problem was resolved by applying a revert to address the issue. **Action Plan** To prevent similar issues in the future, unit tests will be created to avoid this type of failure scenario.
Affected components
Update timeline
- investigating Jan 09, 2026, 02:02 PM UTC
We have identified an issue where some records might not be visible when searching with filters in databases.
- monitoring Jan 09, 2026, 02:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 09, 2026, 02:14 PM UTC
This incident has been resolved.
- postmortem Jan 13, 2026, 05:22 PM UTC
**Root Cause** The issue was caused by a non-optimized query that struggled when handling more than 50 records, leading to problems in database searches. **Resolution** The problem was resolved by applying a revert to address the issue. **Action Plan** To prevent similar issues in the future, unit tests will be created to avoid this type of failure scenario.
Your product runs on more than Pipefy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services