> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/changelog/releases/165.md).

# 165

Appfarm 165 brings a new Files page with internal files, timeouts for Flow endpoints, a way to stop a running Flow from an app, and a faster Action node picker.

| Channel  | Date             |
| -------- | ---------------- |
| Early    | October 26, 2026 |
| Standard | November 2, 2026 |
| Stable   | November 9, 2026 |

## New and improved

### Files

* **A new Files page.** [Resources › Files](https://docs.appfarm.io/reference/resources/files.md) now has three areas: **Internal**, **Public** and **System**. Internal files are only visible to Appfarm Create users in the Solution and have no public URL. They support folders, drag-and-drop upload, rename, move and preview, up to 25 MB per file and 2,000 files per Solution. Public holds your existing resource files, unchanged. System shows what Appfarm AI writes, read only.
* **Permissions for internal files.** Create Private File, Update any Private File and Delete any Private File are granted to the built-in Developer, Maintainer and Owner [roles](https://docs.appfarm.io/reference/security/roles.md). Add them to custom roles that should upload, rename, move or delete internal files.
* **Uploads in Appfarm Create are scanned for malware.** Uploads to Internal and Public show a **Scanning** tag until the scan finishes. A file that fails the scan is shown as **Blocked** with the reason and is never saved. Uploads from apps, Flows and the API are not scanned.

### Flows

* **Timeouts for Flow endpoints.** A [Flow endpoint](https://docs.appfarm.io/reference/flows/api-endpoints.md) has a **Timeout** setting under Advanced, from 1 to 14,400 seconds. When time runs out, the running node fails with a Flow timeout exception, and if the Flow doesn't handle it, the caller gets `504 Gateway Timeout`. Left empty, there is no limit, as before. (DEV-3241)
* **Stop a running Flow from an app.** [Run Flow](https://docs.appfarm.io/library/action-nodes/run-flow.md#stop-a-running-flow) in an app Action can store a **Run ID**. The new Manage Flow action node takes that ID and stops the run, including any Flows it started. Only the person who started a run can stop it. (DEV-2924)

### Sign-in and security

* **SSO sign-in finishes in the browser that started it.** A sign-in whose callback opens in another browser or an embedded webview fails and has to be started again. (SEC-373)
* **Login emails are limited per address.** One-time passwords, login links and password resets are limited to 5 per email address per 15 minutes in each environment. Automated tests that reuse one address may hit the limit. (SEC-560)
* **The Client IP App variable uses the address Appfarm receives the request from.** If your Solution sits behind your own proxy or CDN, the value is that proxy's address. (SEC-735)
* [**Send Email**](https://docs.appfarm.io/library/action-nodes/send-email.md) **attachments from URLs are checked like** [**Web Request**](https://docs.appfarm.io/library/action-nodes/web-request.md)**.** Attachments from private or internal addresses, and attachments over the email provider's size limit, fail. (SEC-512)
* **Filter values must match the property's data type.** A server-side [filter](https://docs.appfarm.io/reference/platform-concepts/filters.md) that receives an object as its value now fails with a data type error instead of matching nothing. This applies to every data type except rich text. A filter on a database connected data source returns no objects instead. (SEC-542)

### Appfarm Create

* **Find Action nodes faster.** The [Action node](https://docs.appfarm.io/library/action-nodes.md) picker is grouped into eight categories, and search also matches common words from other tools, such as "http", "loop" and "toast". Hover a node to see what it does. New nodes are tagged **New** until you first use them. (PRO-371, PRO-373, PRO-374, PRO-376)
* **Right-click menus.** Rows in the Security tables, app cards on the Apps page and font files open their actions on right-click. Context menus can be used with the arrow keys as soon as they open.
* **Image picker in dark mode.** Images in the image picker keep their contrast in dark and light mode, and the picker has a list and grid view. (DEV-3264)

### Logs

* **Schedules and Services log to the Logs view only.** The legacy Schedules and Services log tabs no longer receive new entries. Use the [Logs](https://docs.appfarm.io/reference/operations/logs.md) view instead. (DEV-2482)

### Appfarm AI

* **See what Appfarm AI is doing.** With the panel closed, hover the [Appfarm AI](https://docs.appfarm.io/reference/appfarm-ai.md) button to see the current conversation and its status. When Appfarm AI is waiting for your answer, the button shows an orange dot, and in a background tab the favicon and title show it too. (PRO-365)
* **Long builds continue in a new thread.** When a build thread gets long, Appfarm AI offers to continue in a fresh thread that starts from a written summary. (DEV-3247)
* **Solution memory.** Appfarm AI keeps a memory for the Solution and uses it in every new thread. Review and edit it in Settings › Appfarm AI. It replaces **Agent knowledge**, which is now marked as deprecated.

### Data

* **Large saves hold records locked for less time.** Saving or updating many existing objects now writes them in batches of 500. (COPS-1187)

### Flow DevTools

* **Light mode.** [Flow DevTools](https://docs.appfarm.io/reference/appfarm-client/developer-tools-for-flows.md) follows the theme you picked in Appfarm Create. (DEV-2074)
* **Abort run stops right away.** Abort run now interrupts the node that is running, such as Sleep, Web request or a nested Run Flow, instead of waiting for it to finish. (DEV-2333)

## Fixes

* SSO sign-in failed with "Invalid or expired SSO state" when it started on a host other than the Solution's main URL. Fixed in 165.0.13. (COPS-1315)
* Appfarm Create could show that the Solution was out of [AI credits](https://docs.appfarm.io/reference/appfarm-ai/ai-credits.md) when it wasn't, and credits bought outside Create didn't show up. (DEV-3286)
* The log entry for an app whose initial data failed to load was lost if the tab was closed. (DEV-2390)
* **Has value** and **Has no value** filters on reference properties returned wrong results when written by Appfarm AI. (DEV-3276)
* A date URL parameter read after navigating inside an app came out as UTC midnight instead of local midnight. (DEV-3224)
* Objects turned into text, for example in [Open URL](https://docs.appfarm.io/library/action-nodes/open-url.md) query parameters, showed as `[object Object]`. They are now written as JSON. (DEV-2394)
* [Full-text search](https://docs.appfarm.io/library/action-nodes/full-text-search.md) missed rich text saved before search was turned on, and didn't work on file object classes. (DEV-3270, DEV-3265)
* Appfarm AI refused to add properties to object classes that a Service uses, and gave out Flow endpoint URLs without `/flows/`. (DEV-3222, DEV-3248)
* Flow DevTools brought back cleared runs after a save, and dropped the finished run when you stopped listening. (DEV-3210, DEV-3188, DEV-3189)
* [Agent action node](https://docs.appfarm.io/library/action-nodes/agent.md): param and variable tools are validated when the node is added, and file tool warnings name the right cause. (DEV-3028, DEV-3048)

***

Covers 165 up to 165.0.13.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appfarm.io/changelog/releases/165.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
