If your Apollo sequences or call tasks are missing in Orum, the issue is usually related to task due dates, task type, sequence visibility, list selection, or Apollo permissions.
This article walks through the most common causes and what to check next.
Apollo sequences not appearing in Orum
Apollo call tasks not appearing in the Search List dropdown
Tasks showing up in a specific Apollo sequence but not in All Sequences Due
Cases where one user can see Apollo tasks or sequences and another cannot
This article assumes:
Your Apollo integration is already set up
The affected rep can sign in to Orum
You are troubleshooting Apollo list, sequence, or task visibility rather than call audio quality or login setup
If you still need to complete initial setup, start here:
First, click the Refresh button in the Orum dialer.
This prompts Orum to request the latest active Apollo tasks again. A browser refresh by itself may not fully refresh the Apollo task pull.
If that does not help, sign out and back into Orum, then return to Apollo and test again.
Orum only pulls Apollo tasks that are both:
Call tasks
Due now or past due
Tasks may not appear in Orum if they are:
Scheduled for later today or a future date/time
Not yet due
Email tasks or other non-call task types
If the task exists in Apollo but does not appear in Orum, confirm its due date and task type first.
If a task is missing from All Sequences Due, try selecting the specific Apollo sequence instead.
In known cases, the task appears correctly in the individual sequence even when it does not appear in the broad all-sequences view.
If the task appears in the specific sequence, that usually means:
The integration is working
The task is real and callable
The issue is with how the broader list is being returned or filtered, not with the contact itself
If tasks appear inside the specific Apollo sequence but not in All Sequences Due, the all-sequences list may be at capacity.
In known support cases, All Sequences Due is effectively capped to a limited pool of tasks for the rep/integration session. When that happens, Orum can only work from that returned pool, and filters operate only inside it.
That means:
A task can be valid and due in Apollo
The same task can appear in the specific sequence
But it still may not appear in the broader All Sequences Due list
If your team has a high volume of due Apollo tasks, use the specific sequence whenever possible instead of relying only on All Sequences Due.
A very common Apollo issue is sequence visibility.
If a sequence does not appear in Orum at all, check whether it is set to Private in Apollo.
Apollo sequences that are private may not be returned to Orum consistently. In many cases, a sequence must be shared more broadly in Apollo before Orum can reliably access it.
Ask your Apollo admin to confirm that the sequence is:
Active
Shared appropriately
Not private, if the goal is for reps to dial it in Orum
If only one user cannot see the sequence, compare that user’s access to a teammate who can.
If the sequence or task visibility is incomplete or inconsistent, review the Apollo permission profile.
Permissions related to the following can affect Orum behavior:
Sequences
Calls
Tasks
Viewing private sequences
Editing call dispositions or purposes
Completing, skipping, or modifying tasks owned by other users
If one rep can see the sequence but another cannot, this is often a permissions difference rather than a full integration outage.
A sequence can exist in Apollo but still not be useful for dialing in Orum.
Confirm that:
The sequence has enrolled prospects
The next available step is a call task
The task is already due
If non-call steps or future-dated steps are still ahead in Apollo, the next callable task may not be available in Orum yet.
If Apollo was working before and suddenly stopped loading lists or tasks, the connection may need to be refreshed.
Ask your Apollo admin to check:
Whether the Apollo API key is still valid
Whether the rep’s Apollo access changed recently
Whether the integration needs to be reauthorized or updated in Orum
For setup and reconnection context, see:
This usually means the integration is working, but the broader all-sequences view is not surfacing that task from the returned Apollo task pool.
The most common causes are:
The sequence is private
The users have different Apollo permissions
One user’s Apollo or Orum session needs to be refreshed
Usually because the sequence is private, has no eligible due call tasks, or the rep does not have the right access to it.
