Run history

See every run of a function — who or what started it, how long it took, its logs, input and output — and run it again with the same input.

Every time a function runs — from the Run button, a flow, a work queue, a form, its public address or Ask Axis — the run is kept. Use it to find out why something failed, or to repeat a run after fixing the code.

Before you start: you need Can view on Custom code. Running a function again needs Can run. If you don't see this yet, the owner applies the waiting workspace upgrade — see Upgrade your workspace.

See the runs

  1. Open Functions and pick a function.
  2. Click Runs in the switch at the top of the editor (next to Code and Configuration).
  3. Narrow the list with All, OK, Errors or Timed out. Click Refresh for newer runs and Load more for older ones.

Each row shows the status, what started it (Run button, Ask Axis, Public URL, Flow, Work queue or Form), who, the error if there was one, how long it took and when.

Look at one run

Click a row. Run details shows:

  • The status, what started it, the date and time, and how long it took.
  • The error message, if it failed.
  • Logs — everything the code wrote with console.log, warn and error.
  • Input and Output.

Secret values never appear: they are masked in errors and logs. See Secrets.

Run it again

In Run details, click Run again with this input. The editor fills its test input with the same data so you can run it after fixing the code.

How long runs are kept

  • The list of runs is kept with the status, error and timing.
  • Logs, Input and Output are kept for 14 days. An older run says so.
  • Very long output is cut to keep history small (32 KB of logs, 4 KB of input and output).