Skip to content
MockFlow DocsGet an API key

Fix automations that do not run, runs that are skipped or fail, apps that need reconnecting, Then steps that are not sent and local agent errors.

Updated 1 Nov 20265 min read

Most automation problems show up in three places: the message box at the top of My automations, the run's result in Recent runs or History, and the browser notification you get when a run fails or an automation pauses. Find the message you see below.

Automations are not in the sidebar

  • Automations are part of the current MockFlow workspace with the sidebar. If you do not see the workspace sidebar, see the workspace sidebar.

  • The board menu's Automations section is not shown for local files in the desktop app. Open a cloud board.

  • While you search the sidebar, the Automations group is hidden. Clear the search box.

The automation cannot be saved or turned on

Message

What to do

Automations are on the Max plan. Upgrade to make boards automatically.

Automations save and run on the Max plan only. On other plans you can build one to see how it works. See Automation plans and limits.

You have 50 automations. Delete one you no longer need.

You can keep up to 50 automations. Delete one from its … menu.

Upgrade to Max to use {App}

Apps other than Slack and Trello need the Max plan.

An event shows Not on this connection

Your app's connection cannot deliver that event. Pick At a set time instead.

The button says Pick an app first, Pick when it runs first or similar

A part of the sentence is still empty. Click the highlighted part and choose it.

The automation did not run

  • It is off or paused. Check its row in My automations. Turn it on with its switch, or fix the reason shown for Paused.

  • Monthly runs are used up. The run is skipped with Your Max plan includes 60 automation runs a month and they are used up. Runs reset on the first of the month.

  • AI credits are used up. The run is skipped with Out of AI credits. Credits reset on the first of the month. Runs that use your local agent or add records as they are keep working.

  • The automation reached its own cap. The run is skipped with Monthly limit of N runs reached. Raise it under Edit. Open the automation and raise Runs per month, at most under More options.

  • It runs only when you press Run. Automations set to Only when I press Run never start on their own.

  • The schedule is in another time zone. Schedules use the time zone shown when you set the time. Open When and check it.

A run was skipped and made no board

A skipped run does not count toward your monthly runs.

Reason

What it means

Nothing new since the last run, or nothing matched Filter data

There was nothing to put on the board. Loosen the filter, or wait for new items in the app.

MockFlow AI found nothing to place this time.

The app sent nothing MockFlow AI could turn into items.

Nothing to place yet. It places what the app sends next.

An automation that adds records as they are waits for the app's next event.

The app needs reconnecting

Message

What to do

{App} is not connected

Click Connect {App} in the message, or Connect in Apps.

{App} stopped working or Sign-in stopped working

The sign-in expired or was removed in the app. Click Reconnect {App}.

Paused: Connect {App}. It was disconnected. Paused until then.

Reconnect the app. Automations that paused for it can then be turned on from {App} is connected again.

That app event no longer exists. or The app this automation reads from is no longer offered.

The app changed what it offers. Pick another event or app.

A dot on the Apps button also shows that an app your automations use needs attention. See Connect apps to automations.

The board, frame or space is gone

Message

What to do

Paused with Pick the board again or Pick the {item} again

The board, component or channel the automation uses was deleted or moved. Click the button and pick it again.

Can no longer add boards there. Pick another place under Edit.

You lost edit access to the space, or it was deleted. Open the automation and choose a new place under Where.

This kind of component cannot be kept up to date. Pick another one, or make a new one each run.

Choose a component such as a kanban, timeline or document, or choose A new MockFlow board each run.

This kind of component cannot take records as they are. Pick MockFlow AI under Edit.

Under How, choose AI makes it.

The run failed or the board looks incomplete

Message

What to do

Nothing was drawn on the board this time. Try again in a while.

A temporary problem. Click Run again.

Drawing the board ran out of time, so it may be empty or partly drawn.

Open the board to check it, then click Run again. Asking for less in the instructions or using Filter data helps large runs.

The board did not show it in time. It may still appear; check the board.

Open the board after a moment before running again.

Showing only part of what was read, to fit one board.

The app returned more than fits on one board. Narrow what it reads or add a filter.

You get one notification the first time an automation fails. Further failures in a row stay quiet until a run works again.

The Then step was not sent

When the board is made but the Slack post, email or Google Drive picture fails, the run shows Made it, but not sent and History shows Not sent with the reason.

  • Click Try again in History or in the message at the top of My automations.

  • Check the step's details: the Slack Channel, the email To address or the Drive Folder.

  • Reconnect Slack, Gmail or Google Drive in Apps if their sign-in stopped working.

Local agent errors

Message

What to do

Your local agent is not connected. Open a MockFlow board with the MockFlow Bridge running, then run it again.

Start MockFlow Bridge, open any MockFlow board so it connects, then click Run again.

Your local agent did not pick it up within 10 minutes

Your computer was off or the Bridge was closed. Keep the Bridge running, or switch the automation back to MockFlow AI.

Your local agent did not finish within 15 minutes

Ask for less in the instructions, or let MockFlow AI make this automation.

Your local agent cannot make a type, so MockFlow AI makes it

That type is made by MockFlow AI only, and the run uses AI credits.

Keeping a frame up to date runs on MockFlow AI.

Automations that update a component always use MockFlow AI.

See Run automations with your own AI and save AI credits and Troubleshoot MockFlow Bridge.

Notifications do not arrive

  • Notifications for new boards arrive only when Notify me is on in the automation's Then menu.

  • MockFlow notifications are browser notifications. Allow notifications for MockFlow in your browser settings.

  • Failures and pauses always notify you, but only the first failure in a row.

Was this page helpful?

Sign in to MockFlow

The same account you use in the app and on the API.

Forgot your password?
or
Continue with GoogleContinue with MicrosoftContinue with Apple