All systems operational

Automation Review

Review the platform's background jobs to confirm they are running as expected.

#Business goal

Keep automations reliable and catch failures early.

#When to use this

Weekly.

#At a glance

DetailValue
People involvedAdmin / operations lead
Departments usedOperations, Leadership
Modules usedAutomation, Reports
AI usedAI drafts sequence content; the automation jobs are fixed and run on a schedule
Recommended timelineWeekly
PrerequisitesAdmin access; Email delivery configured for sending jobs

#Step-by-step process

1

Check job status

Review the status of sequences, follow-ups, scheduled reports, and renewal reminders.
2

Read the logs

Confirm recent runs succeeded.
3

Trigger if needed

An admin can run a job manually.
4

Fix failures

Address the cause of any failed run.

#Decision points

Decisions to make along the way

  • Did the jobs run successfully?
  • Does anything need a manual run?

#Approval points

No formal approval gate

This routine has no separate sign-off step, but review your work before it affects clients or finances.

#Success metrics

  • Reliable automations
  • Failures caught early

#Best practices

  • Confirm success rather than assuming.
  • Ensure email delivery is configured for sending jobs.

#Common mistakes

  • Assuming jobs ran without checking.
  • Forgetting the job set is fixed, not a builder.

#Realistic example

In practice

The weekly check shows the sequences job ran, but a scheduled report failed on email; the admin fixes delivery and re-runs it.
Monitoring Routine

System health.

Scheduled Reports

Underlying flow.

Business Workflows

Underlying step-by-step flows.

Contact Support

Reach the DevSphere OS team.

Still need help?

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

Contact Support