All systems operational

Background Jobs & Automation Status

Monitor the platform's background automations — sequences, follow-ups, scheduled reports, and renewal reminders — via automation status and logs.

#Purpose

Confirm background jobs are running and diagnose failures.

#When to use this

When an automation seems not to run or during routine checks.

#At a glance

DetailValue
Required permissionsAdmin access; admin/CEO to trigger a run
Administrator levelCEO / Admin
Portal areas usedAutomation (status, logs, run-now)

#Step by step

1

Open automation status

Review the status of the background jobs.
2

Check the logs

Each run is recorded with its outcome.
3

Trigger a run if needed

An admin or CEO can run a job manually (sequences, follow-ups, scheduled reports, or renewal reminders).
4

Fix failures

Read the log detail and address the cause.

#Approval points

No formal approval gate

This administrative action does not require a separate sign-off, but review carefully before applying changes.

#Security notes

Security considerations

  • Manual job triggering is limited to admins/CEO.
  • Failed jobs can affect outreach, reminders, and reports — investigate promptly.

#Best practices

  • Review logs after important runs.
  • Confirm success rather than assuming.

#Common mistakes

  • Assuming a job ran without checking status/logs.
  • Not reading the error before re-running.

#Troubleshooting

If this happensTry this
A job did not runCheck status and logs; trigger it manually if needed.
A job failedRead the log detail and fix the cause.

#FAQ

Which background jobs exist?

Sequences, follow-ups, scheduled reports, and renewal reminders.

Can I run a job on demand?

Admins/CEO can trigger these jobs manually.

#Keep exploring

#Business modules & workflows

Still need help?

Can’t find what you’re looking for? The DevSphere OS team is happy to help.