Workflow Guidance, the CARTO Connector, and Edits That Survive a Reload

Workflow memory is now called Workflow Guidance. CARTO joins the connector catalogue on your own OAuth credentials, and an edit in a table survives the row reloading underneath it.

A clearer name

• Workflow memory is Workflow Guidance: The name says what it is: the standing guidance a workflow follows, rather than something that remembers on its own.

Connectors

• CARTO, on your own credentials: CARTO is in the catalogue and connects with your own tenant OAuth credentials, so the connection belongs to your account rather than to a shared client.

Edits that survive a reload

• Reference picks are kept: An unsaved reference selection survives the row refetching, so a pick is not lost to a refresh you did not ask for.

• Cell edits stop going missing: An edit in a cell is kept rather than dropped.

• Uploads that start early still finish: A library upload begun before the library has loaded, or during a list reload, completes instead of being abandoned.

• Fewer requests behind a table: The imports list is fetched once rather than for every cell on screen, which shows most on a wide table.

Reporting

• A keyboard date pick holds: Picking a date with the keyboard no longer resets the report period.

• Field calculations on the user overview: Field calculations appear among a user’s actions, so their work is counted where it is read.

Underneath

• Steadier coordination across the cluster: Cluster locking moved onto Redis and debouncing onto an atomic cache claim, which removes a class of stall under load.

• More room for outbound traffic: Outbound HTTP pools are sized for their traffic, and a pool checkout timeout comes back as an error rather than as a hang.