Activity and the audit trail

The console keeps two records of what happens:

• Activity shows the background jobs of the project you have open, such as imports, example generation and evaluations. Everyone can follow them.
• The audit trail shows who changed what in the organization, and when. Only owners can read it.

Activity

Choose Activity at the top of any page. The button shows how many jobs are queued or running. If none are, but a GPU is still in use or being released, it shows a dot instead.

What appears

Each job shows its status (Queued, Running, Completed, Failed or Cancelled), its progress, and the reason if it failed. A Hugging Face import also reports how many rows it imported and why any were skipped.

Training runs, deployments, experiments and published models are not jobs. Their own pages show their status, and the project's Home shows what holds a paid GPU right now.

Cancel or retry a job

You need the member or owner role.

• Cancel stops a queued or running job. Work it already finished stays.
• Retry queues a failed or cancelled job again. Imports, generation and evaluations continue from where they stopped.

Clear finished jobs

Finished jobs stay in the list until you clear them. Choose the cross next to a job to clear it, or Clear all to clear every finished job in the project. Clearing only tidies your own list; other members still see the jobs, and nothing is deleted.

When a job shows an error

A job that stops shows its reason underneath. If the reason could include your own data, the console may hide it and show:

Kind: an unexpected error stopped this. Its details are not shown, because they may contain your data. Retry, or contact support if it happens again.

Common causes are an endpoint answer in the wrong format, a Hugging Face dataset that changed during an import, or a network volume that can't be written to. Fix the likely cause and choose Retry. See Troubleshooting for more.

The audit trail

Owners open Settings at the foot of the sidebar, then Audit trail. Events are listed newest first, 50 per page.

The audit trail can't be searched, filtered, exported or changed.

What is recorded

• Every successful change in the organization: projects, sources, recipes, reviews, versions, evaluations, training runs, deployments, experiments, connections, API keys, published models, members, invitations and the organization's name.
• Downloads of datasets, adapters and job files.
• Joining: accepted invitations and the creation of the organization.
• Billing: opening checkout, opening billing management, and subscription changes.
• Playground use: at most once every 15 minutes per person and project.
• Actions Tensorant takes on your organization, shown as "Platform…", such as "Platform approved access".

Leaving an organization is recorded as "Removed a member", with you as Who.

What is never recorded

• Your content. No prompts, answers, dataset rows, file contents, edits, keys or secrets.
• Refused requests, and viewing pages or data (apart from downloads).
• Your applications' API calls. Keys and usage counts them instead, without prompts or answers.
• Your own account, such as signing in or changing your password.

Limits

When something goes wrong