Changing a Slack step's connection wipes its Message field - cannot repoint steps (classic builder)

We re-authorized our Slack connection (new connection name: "FAST BOT 2026") after our old Slack connections stopped working, and we have been repointing every Slack step in our workflows to the new connection. That worked on most workflows, but in the three classic-builder workflows below, changing a step's Slack connection in the editor clears the step's Message field: the rich message editor is replaced by an empty plain textbox, so the step cannot be saved with the new connection ("Message is Required"). Discarding the change restores the original message and the old connection. These steps also show a pre-existing "Error in this step" flag.

Affected workflows and steps:

1. "1.4 Project Report -> CU,G.M.Cal Event" - https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTZhMDYzMzA0MzU1MjY4NTUzMjUxM2Ei_pc

Steps: "notify team in office channel", "Suggest message for received docs pt1", "Suggest message for received docs pt2", "Reminds Employees to Add email to form submission" (direct message).

2. "1.9 Close Project -> automations, CU, GM etc" - https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTZlMDYzMzA0MzI1MjY4NTUzNzUxMzci_pc

Step: "notify team in office channel".

3. "CLONE - [New Project Form Filled - back up" - https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTZlMDYzMzA0MzE1MjZjNTUzZDUxMzci_pc

Steps: "notify team in office channel", "Suggest message for received docs pt2" (same message-wipe), and "Reminds Employees to Add email to form submission" (direct message): on this one the message survives, but the recipient user does not resolve under the new connection (it changes to a deactivated user), so it also cannot be saved as-is.

Could you please repoint these steps to the "FAST BOT 2026" Slack connection, preserving each step's channel, message text, recipient, and mappings exactly as they are now? I authorize the Pabbly Support team to access my account and make these edits if needed.

Also, is the message-clearing behavior a known issue with a fix on your side? It only happens on some classic-builder steps; others switched normally.

Thank you,

Igor, FAST Restoration