Tasks

Work ClaimPod does on its own. This page covers Tasks - what has run - and Schedules - what will run - because the question spans both: did my recurring import actually happen?

Who Can See It

Tasks is open to User and Administrator. Schedules is Administrator only.

Tasks

Column	What it shows
ID	The run
Task	What kind of work it was
Status	Pending, Processing, Completed, Failed or Canceled
Started, Finished	When
Duration	How long it took

Schedules

Column	What it shows
Task	What it runs
Trigger	When, in plain words
Next Run	When it is due
Last Ran	When it last went, or Never Ran
Active	Whether it is running at all

Actions

Action	What it does	When it is offered
Create	Adds a schedule	Administrator, on Schedules
Run Now	Runs a scheduled task once, immediately	Administrator
Edit / Delete	Manage a schedule	From the row menu

Run Now does not change the timetable: the next scheduled run still happens when it was going to. Deactivating a schedule stops it without losing it, which is usually what you want over deleting.

The Follow-up Sweeps

Two of the schedulable tasks fill work queues rather than moving data: Follow-up Claims chases submitted claims the payer has not answered, and Follow-up Visits finds visits that have gone unbilled. Both take a Threshold (days) parameter - the age at which something becomes worth chasing - and both close their own items once the claim is answered or the visit is billed.

Neither runs until someone schedules it. Until then the follow-up queues stay empty, which is a configuration choice rather than a fault. What the items look like once they arrive is on The Queue Processor.

States

• Never Ran on a schedule that has not fired yet.
• No schedules yet on an empty list.

Related: Schedule a Recurring Task · Work Queues · Connections · Imports