How long did you wait? It may sometimes take up to a few minutes after a start or restart before FME Flow is fully up and running. If the problem persists for more than say 5 minutes I’d start looking deeper into it. In that case the FME Flow Troubleshooting Guide is the best place to start.

It was definitely past 5 minutes, and now over 12 hours. Thanks for linking the troubleshoot guide -- I’ll keep looking into this. Cheers!

Yeah, that’s definitely an issue! My gut feeling says it may have something to do with the accounts under which the various FME Flow services run.

What was the solution to this?

We had a DB account that had the necessary roles to access the tables, but since the account didn’t have direct access to the tables, we were seeing that message.

We switched to the DB owner account, and problem solved!

@brian.atuh can you elaborate some on what exactly the fix was. Was the owner of a table not the fmeflow user or was it something else?

I am facing this issue now. FME Flow works when I access it from localhost on the web server itself, but I get this error when logging into Flow from the internet (i.e. my laptop at home).

Distributed set up. Engine on one machine, Core and web on another, with FME database in Azure Postgres managed db.