VentsislavTasev
Quickbase Staff
Joined 5 years ago
User Profile
User Widgets
Contributions
Our Monthly Release Window Is Moving to Wednesday Nights
Starting in March, we’re updating when we roll out our monthly major release. Instead of releasing on Sunday morning, we’ll now deploy our major release at 11:00 PM Eastern Time, usually on the second Wednesday of each month. This new window falls during a period of low platform usage, which helps us minimize risk while continuing to deliver new capabilities and improvements. Important - nothing else about our release process or the customer experience is changing. New major release window: 11:00 PM ET on the second Wednesday of each month (starting in March)* Minor releases (“patches”): Continue on Wednesdays at 11:00 PM ET as usual, except on the week of the major release This help article outlines our 2026 release schedule. *The second Wednesday of each month, except for certain months where major US holidays occur earlier in the month. In those cases, the monthly major release will typically be on the third Wednesday of the month. Quickbase reserves the right to adjust the schedule as needed, but will strive to provide at least one month’s notice for any changes to the published schedule You’ll still see the same level of quality, testing, and monitoring you’re used to. We’ll also continue to provide our standard release notes and communications. What this means for you For most customers, this change simply means marking a different day/time on your calendars: If your team runs post-release validation or checklists, you may want to move those to early Thursday morning (in your local time zone). Any integrations, automations, or internal runbooks that reference our Sunday release schedule should be updated to point to the new Wednesday night window. If you don’t currently take any specific action around our monthly major releases, you likely don’t need to do anything at all. While customer-facing issues from our major releases are very rare*, this schedule ensures we continue to deploy during a low-traffic window with our teams fully prepared to monitor and respond if needed. *To be notified in the event of a disruption subscribe to our status page and be among the 1st to hear about it. FAQs Q: What exactly is changing? A: Only the timing of our monthly major release. It’s moving from Sunday morning to 11:00 PM ET on the second Wednesday of each month. All other aspects of our release process remain the same. Q: When does this change take effect? A: The new schedule begins in March. The first major release under this new cadence will occur at 11:00 PM ET on the second Wednesday of March (03/11). Q: Are minor releases or patches changing? A: No. Weekly minor releases (patches) will continue at 11:00 PM ET every Wednesday, except in the week of the monthly major release, when that window is used for the major release instead. Q: Will there be downtime? A: We do not anticipate any change in availability compared to our current Sunday release window. Our updates are designed to be low-disruption, and we use the same safeguards—testing, gradual rollout where applicable, and monitoring. Q: My team has a Sunday checklist today. What should we do? A: If your team currently validates your applications or integrations after our Sunday release, we recommend updating those checklists to run after the Wednesday 11:00 PM ET release, typically early Thursday morning in your local time. You don’t need to change what you check—only when you run those checks. Q: How will we know what’s in each major release? A: We’ll continue to publish release notes and related documentation as we do today. The content and level of detail in those notes will not change with this schedule update. Q: Who can I contact with questions? A: Please reach out to your account team through your usual channels, and we’ll be happy to help you plan for the new schedule.Re: Pipeline that retrieves list of pipelines?
Please be informed that our Pipelines admin console connected table provides the same realm-level overview of pipelines that you are looking for. Check out this help article for more details. Keep in mind you must be on Business or Enterprise plans in order to have access to that capability.Upcoming change: More consistent loop behavior when a step fails in conditional logic
At a glance: After February 10th, Pipelines will handle errors in loops more consistently: If a step fails during one loop iteration—even when that iteration includes an IF/ELSE branch—the pipeline will skip only that iteration and continue to the next. The full pipeline will only stop if you explicitly use a STOP step. Why we’re making this change In Pipelines, errors typically stop a pipeline run. That’s a safe default: if something unexpected happens, the pipeline pauses, allowing you to review and fix the issue. Loops are the notable exception. In many real-world automations, it’s better to keep going even if one item fails—especially when processing a list of records (like invoices or purchase orders). Today, loops already behave that way: If one loop iteration fails, Pipelines usually skips that record and continues with the next one. But we found an inconsistency: If an iteration includes conditional branching (IF/ELSE) and the logic step fails along that path, the entire pipeline run stops, rather than skipping just the one problematic iteration. We’re updating Pipelines so that loop behavior is consistent, regardless of whether an iteration includes an IF/ELSE. Learn more about conditions in our help article. A quick refresher: How errors normally work in Pipelines Simple pipeline (no loop) Use case: When a new invoice is marked “Approved,” update a related project record. Example flow: Trigger: Invoice is updated (Status = Approved) Step: Find the related Project Step: Update Project “Invoiced Amount” If any step fails (for example, the Project can’t be found), the pipeline run will stop, and you’ll see the error in the activity log. Today, the HTTP channel is an exception because it provides more built-in options for handling responses and failures. We’re also planning improvements to error handling over time, so stay tuned. Loops: What happens when one record fails Loop without conditional branching (current behavior) Use case: Every night, process all “Ready to Pay” invoices. Example flow: Trigger: Scheduled (nightly) Step: Find invoices where Status = “Ready to Pay” Loop: For each invoice Update invoice status to “Submitted to Accounting” Write a note back to the invoice If there are 10 invoices and invoice #6 fails (maybe it was deleted, locked, or missing required fields): Pipelines will skip invoice #6 Continue processing invoices #7–#10 The run will not fail entirely The activity log will show which invoice failed and why This is the behavior many customers expect (and rely on) when automating batches of records. The inconsistency we’re addressing Loop with IF/ELSE branching (current behavior in some cases) Now, let’s add a very common pattern: decisions as part of each loop iteration. Use case: Nightly invoice processing with a rule: If the invoice total is over $10,000, send it for additional approval Otherwise, submit it to Accounting Example flow: Trigger: Scheduled (nightly) Step: Find invoices where Status = “Ready to Pay” Loop: For each invoice IF Total > $10,000 Create an “Approval Request” record Notify an approver (email/Slack/etc.) ELSE Update invoice status to “Submitted to Accounting” What can happen today: If the condition step fails in a single iteration (for example, invoice #6 amount is missing), the pipeline run will stop completely—even though you still have invoices #7–#10 to process. That’s inconsistent with how loops behave in other scenarios. The upcoming change With this update, the loop will behave the same way regardless of whether conditional logic is part of the iteration. If a step fails during one loop iteration: The pipeline will skip that one invoice Continue with the next invoice The activity log will still capture the failure for visibility and troubleshooting What won’t change If you want the pipeline to stop intentionally, you still can The STOP step is the right tool when you intentionally do not want the pipeline to continue (for example, when a condition indicates the run should end). This upcoming change does not remove that control. It simply ensures that unexpected failures in one loop iteration don’t take down the whole run when conditional branching is involved. What this means for you Most pipelines won’t require any changes. But the planned for February 10th change is especially relevant if you: Use loops to process batches of records (invoices, purchase orders, requests, etc.) Use IF/ELSE branching inside the loop to apply different actions per record Expect the pipeline to continue even if one of its iterations fails If you previously relied on the pipeline stopping in this scenario, consider adding a STOP step intentionally when you want that behavior.Release Notes Are Getting a New Home
As part of our ongoing fit & finish focus—making the Quickbase experience smoother, clearer, and more consistent—we’re giving Release Notes a fresh home in a dedicated Quickbase app. This isn’t just a new location; it’s a better way to discover what’s new, track what matters to you, and plan ahead with confidence. Starting this fall, Release Notes will be faster to scan, easier to search, and more useful for your day-to-day work. Timeline September 9: We’ll publish Release Notes in both places (our help center and the new Quickbase app). October 7: Release Notes will be available only in the Quickbase app. We’ll share the direct link in your monthly email and in-product, and you can bookmark it for quick access. Why we’re making this change Today’s Release Notes live in our help center and can be tough to navigate and search across. That makes it harder for customers to find what matters to them and for our teams to keep everything consistent and up to date. A purpose-built app lets us fix that by centralizing content and making it more discoverable. What you’ll get in the new Release Notes app Powerful search & filters – Find updates by product area, plan, or feature types; sort and group across multiple releases. Clear, scannable layout – Short summaries with optional detail when you need it. “Coming soon” visibility – See a sneak peek of important changes on the horizon, including expected timing so you can plan ahead. Email that matches your pace – Keep the monthly summary. Prefer more frequent updates? Opt in to more frequent notifications. History at your fingertips – Older release notes hosted in our help center will be linked for continuity. Impact defects prioritization – Declare interest in specific defects and get notified when they are resolved. Service status connections – Where applicable, updates will link to related posts on our Service/Status page. An example screenshot (subject to change): What’s not changing You’ll still get a monthly Release Notes email—we’re just making it more useful and pointing you to the app as the single source of truth. The product continues to improve at the same pace; you’ll simply have a better way to discover, track, and engage with those changes. Key dates & how to prepare Now–Sept 9: Keep using Release Notes in the help center. Sept 9–Oct 7: Release Notes will appear in both places while we transition. We’ll include a link to the new app so you can explore it early. Oct 7 onward: Release Notes will be available exclusively in the Quickbase app. Thanks for being part of the Quickbase community. We can’t wait for you to try the new Release Notes experience—built to make finding the updates that matter simple, fast, and transparent. Click here to access the Release Notes App! FAQs Q: Where do I find the new Release Notes app? A: We’ll include the link in the monthly email and in-product. Save it as a bookmark for quick access. Q: Will old notes still be available? A: Yes—previous release notes will be linked from the app so you can reference historical changes. Q: Can I keep monthly emails only? A: Absolutely. Monthly remains the default. You can opt in to weekly or daily notifications if you want more frequent updates. Q: How do I share feedback? A: The new app will have a dedicated feedback form.Scaling with Control & Confidence
At this year’s Empower Pro, we explored a topic that’s core to every Quickbase customer — how to scale with control and confidence. As organizations embrace no-code and AI-driven app development, governance is no longer optional; it’s the foundation that keeps innovation safe, compliant, and sustainable. Our session, Scaling with Control & Confidence, was led by Lyla Rozelle, Rayna Stoycheva, and Ventsislav Tasev. They unpacked the newest tools and upcoming features designed to help admins and builders collaborate, move faster, and stay in control. Why Governance Matters in the Age of AI No-code platforms have unlocked creativity across business lines, but they’ve also blurred the line between IT and operations. Builders crave freedom to experiment; admins need assurance that what’s built can scale securely. Governance is the bridge between those worlds — ensuring builders can innovate with confidence while admins can trust that the environment is safe. Three industry trends make this balance more important than ever: AI-driven development is accelerating app creation — and the risks that come with it. Distributed workforces are empowering citizen developers across every department. Enterprise-scale adoption means mission-critical systems are now built on no-code. Quickbase’s governance strategy rests on three pillars: Discover, Protect, and Control. Here’s what’s new across each one. Discover: Seeing Your Account and Apps Clearly A Revamped Account Summary Managing an account shouldn’t require detective work. The new Account Summary page gives realm and account admins a single, self-serve view of: Contract details and plan limits Usage data from Platform Analytics Admin contacts and support links Now you can track usage, drill into app details, and explore new features — all from one dashboard. It’s cleaner, faster, and designed for self-service. AI App Intelligence (Beta) Ever inherited an app and thought, “What does this even do?” AI App Intelligence answers that question in seconds. It scans your app and summarizes its purpose, key tables, roles, and most-used fields — perfect for new builders or anyone auditing an existing app. Paired with Visual Builder, it gives you a living blueprint of your app without digging into every setting. This feature is currently in open beta for Business and Enterprise plans. Protect: Safeguard Data Without Slowing Innovation Enterprise Malware Scanner As Quickbase apps handle more external documents — bids, contracts, vendor uploads — protecting that data becomes mission-critical. Our new Malware Scanner, powered by Amazon GuardDuty, scans uploaded files automatically via Pipelines. You can configure actions based on scan results: Restrict downloads of suspicious files Delete infected attachments Notify admins or security teams It’s quick to implement, easy to customize, and available now on the Enterprise plan. Control: Manage Access and Deploy Changes with Confidence REST APIs for App Access Managing who gets access to what just got easier. With new REST API endpoints, admins can: Add, update, or remove users, user groups, and email domains (trustees) programmatically Retrieve all app roles automatically These APIs make it possible to integrate Quickbase with your HR or identity systems — ensuring access changes sync instantly when people join, move, or leave. Governance Core Apps & Admin Console Connected tables For admins who want a single command center, the Governance Core Apps (available in the Exchange) provide out-of-the-box dashboards and workflows powered by Admin Console Connected (ACC) tables. New upcoming tables — User Groups/Email Domains and Group Access — make it even easier to spot external domains and track which apps groups can access. Once connected, these apps turn governance data into action. Application Lifecycle Management: Native and Intuitive Under the hood, our ALM capabilities are powered by Quickbase Language (QBL) — the foundation for all ALM workflows. QBL defines your app’s schema in a structured, portable format, enabling accurate deployments between environments. The latest version, v0.12, now covers nearly every solution component, including apps, tables, fields, reports, charts, dashboards, pipelines, and connected tables — with support for emails, additional pipeline channels, and document generation coming soon. Application Lifecycle Management (ALM) is evolving from a complex setup into a native experience built in experience right into Quickbase. With the upcoming ALM UX, you’ll be able to: Create Dev/Test/Prod environments Deploy changes with version control and approvals Review a full deployment history with audit trails The first beta version is focused on more experienced builders, with plans to make it even easier for nontechnical users. Availability: Business plan: Dev + Prod environments for smaller solutions. Enterprise plan: Adds a test environment, approvals, extended history, and solution APIs. Scaling Safely, Building Boldly Governance isn’t about restriction — it’s about enabling innovation without fear. From AI-powered insights to automated protection and native deployment workflows, these updates make it easier than ever to build fast while staying in control. Together, these innovations embody Quickbase’s belief for proper governance: Builders can move faster. Admins can breathe easier. And your organization can scale with confidence. Interested in exploring these features or joining a beta? Reach out to your Quickbase account team or visit the Community for follow-up resources from Empower Pro 2025.Data Change Logs Just Got Smarter!
Having visibility into what changed, when, and by whom, and being able to restore previous values is essential to every software we use nowadays. This is even more important for maintaining trust, accuracy, and control in your Quickbase apps. That’s why we are rolling out a major upgrade to our Audit Logs and particularly to Data Change Logs - giving admins a more powerful, reliable way to track and recover data changes with (almost) zero setup required. What’s New in a Nutshell All scalar fields are now tracked by default once auditing for an app is enabled - no manual enabling needed Only actual field changes are logged - cleaner, more relevant audit trails App admins can now restore changed and deleted values - right from the app audit log Existing field property repurposed - now controls presence in change logs, not logging behavior See full release notes Let’s unpack the details. Easier Setup: Track All Scalar Fields Automatically Previously, tracking data changes required manually enabling individual fields one by one. Now, all scalar fields (like text, numbers, dates, checkboxes, and more) are automatically audited as soon as auditing for an app is turned on. Realm admins can enable data change logs for a particular app from the Admin Console Apps page: As soon as data change logs for an app are enabled, we will start tracking any data changes for all scalar fields in the app. The changed data will be stored at a record level. Here’s an example data change log event for a single record (both in app and realm audit logs): Once you click on the “View data changes” link, the following modal is displayed: The pop-up will contain the previous and current values for all fields from the record where data changes have been made. That same information is also available in JSON format in the CSV export, as well as in our Audit REST API. A Smarter Use of a Field Property We’ve also updated the meaning of the Track field property (Table settings ---> Fields ---> Field Properties) Before: This determined whether the field was tracked at all: Now: All scalar fields are always tracked. The repurposed field only controls whether the field is always shown in the record change log, no matter if the field data has been changed or not: If you already have an app where data change logs had been previously enabled, we will automatically start tracking all fields. However, you may want to do a clean-up and uncheck the repurposed checkbox for some fields to avoid them being always unnecessarily present in the change log entries. You should also keep in mind that if you disable data change logs for an app that had tracking for certain fields already enabled, the setting for these fields will persist the next time you enable data change logs for that same app. Restore Changed Data Instantly This one’s a game-changer: App admins can now restore a field’s previous value directly from the app audit logs. This works both for updated and deleted records. Whether it was a bulk update gone wrong or someone changing the wrong record, app admins can recover from data mistakes in seconds - no need to dig through manual backups, contact tech support or manually re-enter data. What you need to do: Locate in the logs the record that you want to restore, click “View data changes” Select the fields you want to restore - all of them or specific ones Click “Restore previous values” Upon a successful restore, you should see a message like this: You can also restore any deleted record as a new record: • Note • Keep in mind that the data restore option is available only in the app audit log. Data change logs are available in the realm logs, but realm admins do not have the ability to restore data. This is intentional, as we would like to keep the restore closer to where the data lives. Designed to Scale Some of you generate millions of audit events every single day. As part of this change, we thoroughly evaluated the platform performance to ensure app experience and audit performance are not impacted. The new changes are not going to affect your app space entitlements – audit is a separate service. We also decided to retain the existing limit of 50 auditable apps per realm. While this may change in the future, we want to better understand your usage patterns, compliance needs, and platform behavior before potentially enabling higher app limits. The Big Picture Data change log updates are part of a broader investment in powerful, scalable audit capabilities. Read our recent blog post for details on other recent audit improvements. Try It Today If you’re already using Audit Logs, these enhancements are live now. Easy setup. Built-in restore. Smarter logs. Less noise.
