Use Features and Publish in Chatflow Studio after a publish toast closes

User intention

Use Features and Publish in Chatflow Studio.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0

Watch the Features and Publish controls after the publish-error toast disappears. Neither opens its panel during the subsequent click attempts.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

After the toast disappears, Features and Publish respond to clicks again.

How is it judged?

01 · Given

Restore the data and starting state.

On a Chatflow Studio page, a failed Publish Update attempt displays a validation toast above the Features and Publish controls; closing it starts a fade-out.

02 · When

Perform the interaction.

The person dismisses the toast, immediately clicks its center during fade-out, then uses Features and Publish after the toast disappears.

03 · Judge

Rationale: A validation toast is temporary feedback rather than a lock on Studio. Relinquishing its hit area when it disappears lets the user continue using the controls beneath it.

Require

Once the toast is visually absent, the underlying Features and Publish controls receive pointer input and remain operable.

Allowed