Import Flows - 30+ seconds to open in the Editor

I accidentally connected a newer AP version to my old AP version and the new version starting overwriting data and corrupted my original instance. Somewhere in the connection (prob the first 30 seconds) I exported all flows.

The solution was to create a new database, new container instance of AP and then import the flows I exported. Unfortunately, I didn’t realize that I needed to recreate the connections first so I did that after I imported and inspected all flows.

The only noticeable issues:

  1. 2 or 3 of the flows (the ones a bit more complex) now take 30+ seconds to open in the editor.
  2. Another significant item is that a the Webhook Trigger now does not like some POST requests and only treats them as GETs now. I had to recreate some flows to use query string or a post that works. For instance - I have an application that uses Node to create a post request and the Trigger treats this as a GET. This worked before the upgrade. Posts from Twilio requests still work as they did prior.

Last thing I did Is created an instance clustered in Docker Swarm and after some work seems to work. I decided to dump the postgres DB and Restore on the new cluster DB and the same behavior with the editor loading 30+ seconds for the larger flows. I have not yet tested the POST issue.

Any idea if the database is corrupt, if I can fix it, maybe I should start new - create connections and then import the flows?

Any help would be great!

Hi @shawnbure

Is there steps with large payload? If yes, can you try to retest them in the newer version