# Does anything have to happen without a person?

> 48 Flow actions and 43 Apex methods, publicly documented and counted. What runs unattended matters less than what happens when one of those runs fails partway.

*Buyer's guide · Question 6*

## Does anything happen *without a person*?

Ask for a count you can check, then ask what happens when one of those runs fails.

For Salesforce admins and whoever owns operational risk for automated processes.

Last verified 21 Aug 2026·Sources: CloudFiles documentation·v1.0 How this page is sourcedPublished by CloudFiles. The action and method counts are drawn from our own public documentation and independently countable there; the failure-handling behavior is CloudFiles-confirmed by engineering, not a third-party document.

## The count
**48 Flow actions and 43 Apex client methods**, publicly documented, counted 17 August 2026. Anyone can recount them from the published list; the number isn't a claim you have to take on faith.

Source: [CloudFiles Flow actions reference](/salesforce/flow-actions). Retrieved 21 Aug 2026.

## What happens on failure
A count of what can run unattended tells you the surface area. It doesn't tell you what happens when one of those runs fails partway, which is the part that actually costs you.

- Large uploads **retry** automatically.
- Other operations do **not** retry.
- A failed multi-step run can leave the record in a **partial state**, some steps applied, others not.

Source: [CloudFiles error-event documentation](/salesforce/error-event). Retrieved 21 Aug 2026.

## What to ask any vendor

- Is a failure visible to an admin, or does it fail silently until a user notices something missing?
- Is a partial state flagged anywhere, or does it just sit there until someone stumbles on it?
- Which specific operations retry, and which don't, in writing, not “most things retry.”

## What your answer means
**Nothing runs unattended** in your workflow: automation reliability isn't a real requirement for you. Skip this criterion when comparing vendors.

**Anything does:** require a demonstrated failure mode from any vendor, not a features list. Ask them to show you what an admin actually sees when a step fails.

## Where this stops
This page settles automation reliability only. Identity and folder structure are separate questions in [the guide](/salesforce/document-management/guide#questions); so is cost.

## *Check* my working

Most readers won't need this. If a specific failure mode worries you, say what's in the way.

- Report: written assessment, two to three working days.
- Reader: a person. Not a bot, not an auto-reply.
- Call: only if you ask. We won't ask twice.
- Fields: four. No phone, no company size, no mailing list.

**What happens next**

One chip, one line, one email.

A contact form follows this section.

Last verified 21 Aug 2026·Reviewed quarterly·v1.0