Jobs

Jobs are the background-processing layer underneath every workflow, sequence, and bulk operation in Custral. Most users never touch the Jobs surface directly (workflows and sequences run on it on their behalf) but it is exposed for two cases:

• Migrations: large one-time imports or schema changes.
• Scheduled queries: recurring operations that run on a schedule over a filtered set of records or conversations.

​

How it works

Jobs run in the background so they don’t block your work. If a job fails, Custral automatically retries it a few times before giving up; persistent failures are surfaced on the Jobs screen for you to inspect or re-run.

​

What runs as a job

• A workflow run.
• A sequence step.
• An import or one-off bulk operation.
• A scheduled query or recurring task.
• Periodic refreshes of data pulled from connected apps (e.g. GitHub pull request status).

​

Observing a job

Open Settings → Jobs to see currently-running and recently-failed jobs. Each row shows the job’s details, its current state, and (on failure) the error message. Re-running a failed job runs it again with the same input.

​

See also

• Migrations
• Edges & logic