If a call task is showing up in a different Orum list than you expected, or if some due tasks seem missing, the reason is often how the connected platform returns tasks to Orum.
Orum does not use the exact same task-loading logic for every integration. The source system’s sorting, filtering, and API limits affect what appears in Orum first.
How Orum pulls tasks from HubSpot, Outreach, Salesloft, and Salesforce
Why a task may appear in one Orum list but not another
Why a task can be due in your source system but still not be easy to find in Orum
What to try before contacting Support
For task-based workflows, Orum typically expects the task to be:
A call task
Assigned to the rep who is dialing
Due now or past due if the source system uses task due dates for eligibility
For broader troubleshooting steps, see:
Integration | How tasks are pulled in Orum | What to expect |
Salesforce | Orum follows the report’s own sorting and filtering. | If the report order changes, Orum follows that order. |
Outreach | Orum pulls currently due tasks, but Outreach does not return them in a fixed order. | A task may not appear in a predictable oldest-to-newest order. |
Salesloft cadence actions | Orum pulls currently due cadence actions and Salesloft sorts them by last modified date, newest first. | Recently changed actions may appear before older ones. |
Salesloft one-off tasks | Orum pulls currently due one-off tasks and Salesloft sorts them by due date, newest first. | One-off tasks can behave differently from cadence tasks. |
HubSpot tasks | HubSpot tasks are sorted by last modified date, newest first. Orum then applies the due-date filter after retrieving the first batch of tasks. | A due task may not appear in All Due Tasks if many more recently modified tasks are ahead of it. |
HubSpot lists | HubSpot contact lists use HubSpot’s own default sorting. | List order comes from HubSpot, not Orum. |
A task can be real, assigned correctly, and due now, but still show up in a different Orum list than you expected.
Common reasons include:
The task belongs to a different sequence, cadence, report, or source list than the one you are checking
The source platform returns tasks in a different order than you expect
A broad “all due” view contains more tasks than can be surfaced at once
A platform separates sequence/cadence tasks from one-off/manual tasks
This is why a task can sometimes be visible in a more specific list, but harder to find in a broader catch-all list.
HubSpot behaves differently from some other integrations.
For HubSpot tasks:
Tasks are sorted by last modified date, newest first
Orum retrieves tasks in a limited batch first
The due-date filter is applied after retrieval, not before
In practice, this means a task can be due in HubSpot but still not appear where you expect in Orum if a large number of more recently modified HubSpot tasks are returned first.
If your team is relying on a broad list like All Due Tasks, this behavior is more likely to matter.
Outreach and Salesloft can also create confusion, but for different reasons:
Outreach does not provide a fixed, reliable oldest-to-newest order for task retrieval
Salesloft handles cadence actions and one-off tasks differently, so the same rep may need to check the correct task type and list
Refresh the current list in Orum
If needed, use Reset to pull the latest tasks again from the connected platform
Confirm the task is:
assigned to the correct rep
a call task
due now or overdue, when applicable
Check whether the task belongs to a more specific sequence, cadence, report, or HubSpot list rather than a broad all-tasks view
If you are in HubSpot, compare the result in:
the broad due-task view
the specific source list or task grouping you expect the task to belong to
If you use HubSpot, this can happen because HubSpot returns tasks by last modified date, and Orum applies due-date filtering after retrieving the first batch of tasks.
Tasks usually are not moving randomly. More often, they belong to a different underlying sequence, cadence, report, or task type than the list you are checking.
Reset is useful for re-pulling tasks, but the ordering and task-selection behavior still depends on the integration you are using.
