Failed workflow runs now explain what went wrong

When a workflow run fails, General Input now tells you what happened in a sentence or two of everyday words, instead of showing the error the run printed. You see it in the failure email and push notification, on the run's page on the web and in the mobile app, and in the web's list of runs. The original error is still there under Show details, so you, your specialist, or anyone technical can see exactly what the run reported.

How it works

• Written as the run fails. The model your workspace uses for background tasks reads the run's error, the workflow's name and description, and what the failure came down to: the workflow itself, a service it uses, its AI model, or billing. It writes what went wrong and whether you need to do anything.
• It says what to do only when there is something to do. A connection that dropped for a moment usually passes on its own, a refused sign-in means reconnecting that account, and a mistake in the workflow's own steps is something its specialist can fix.
• It costs you no credits. We cover the cost of writing it.
• Your notice never waits long on it. If the explanation takes more than a few seconds, the notice goes out with the original error, and the explanation appears on the run's page once it's ready.

Also shipped

• A run that failed because a service it calls dropped the connection is no longer described as a problem on our side.
• When there is no explanation, the failure email now shows the run's actual error instead of a bare heading.