Skip to main content

Common issues

Problems that come up again and again, what causes them, and how to fix them.

All flows stop after the trigger​

What you see: Flows start – the trigger fires and an execution appears in the Executions list – but nothing happens after that. The execution stays Pending, and this applies to every flow, not just one.

Cause: Almost always the Business Central job queue is not running. AutoFlow runs each flow in the background through the job queue, so the trigger can still create the execution, but no step after it is ever picked up.

How to fix it:

  1. Search for Job Queue Entries and look at the AutoFlow entries. If they sit in status Ready and never start, or are On Hold, the job queue is not processing them. Select the entries on hold and choose Set Status to Ready.
  2. On-premises and in containers: make sure the Business Central Server instance has the task scheduler enabled (setting Enable Task Scheduler). Without it, no job queue entry runs at all. Containers are often created with the task scheduler switched off – turn it on and restart the instance.
  3. Check that the user the job queue runs as is still enabled and has the permissions the flow needs.

Once the job queue runs again, the pending executions continue on their own.

Setting or using a credential fails​

What you see: Saving a secret on an AutoFlow credential fails, or a flow that uses a credential fails – typically with a message such as An encryption key is required to complete the request. or Encryption is either not enabled or the encryption key cannot be found.

Cause: AutoFlow stores credential secrets encrypted with your Business Central data encryption key. If data encryption is not turned on, or the key is gone, no secret can be written or read. On Business Central Online, Microsoft manages the key, so this is an on-premises and container issue. It is especially common in containers (for example environments created through Alpaca): the encryption key is typically lost whenever the container is recreated or reset, while the database still says encryption is on.

How to fix it: open Data Encryption Management in Business Central.

  • Encryption is not enabled – choose Enable Encryption, then enter your secrets.
  • You have an exported key file – choose Import Encryption Key and select the file you saved when encryption was set up. Everything stored before works again, nothing has to be re-entered.
  • The key is lost and there is no export – the stored secrets cannot be recovered. Disable encryption and enable it again, so that a new key is created (if encryption still shows as enabled, you must do both steps – just enabling it again changes nothing). Then re-enter the secret on every credential.
Store your encryption key safely

Right after you enable data encryption, choose Export Encryption Key and keep the file – and the password you protect it with – somewhere safe, for example in your password manager or key vault, not on the server or inside the container. Without that file, a lost key means every stored secret has to be entered again.

A lookup or auto-complete does nothing​

What you see: In a step or trigger, you choose the … button to pick something from a list – a table, a page or similar – and nothing opens. Or you start typing in such a field and no suggestions appear.

Cause: AutoFlow loads the data behind these lists in the background. While it is still loading, the lookup and the suggestions stay empty.

How to fix it: Wait a moment and try again. Once the data is loaded, the lookup opens and auto-complete works as usual.