Workday displays This task is not available when a user opens a My Tasks or email link for a business process step that is no longer actionable under their current session—most often because a peer in the same role already submitted it, locked it with Save for Later, reassigned it, or the user is signed into the wrong Candidate vs. Worker account. A status of Waiting on Initiator (or Awaiting Action on the Initiation step) means the starter saved the transaction as an unsubmitted draft, or an approver used Send Back to return the event to an initiator who has not resubmitted—or can no longer open—the step.
Instead of asking users to clear browser cache blindly, an administrator can pinpoint the exact state of any stuck step in under sixty seconds from the event’s Full Process Record.
Diagnostic Table: Match the Symptom to the Exact Root Cause
| What the User or Admin Sees | Underlying Workday Mechanism | What to Check on Full Process Record |
|---|---|---|
| What the User or Admin SeesEmail link shows ‘This task is not available’ right away | Underlying Workday MechanismAnother user in the same role already completed, canceled, or reassigned the step | What to Check on Full Process RecordProcess tab -> check Status (Step Completed, Canceled, or Reassigned with original assignee in the For column) |
| What the User or Admin SeesStep still shows In Progress, yet peers get ‘This task is not available’ | Underlying Workday MechanismOne recipient clicked Save for Later, which removes the My Tasks item from every other recipient | What to Check on Full Process RecordProcess tab / All Actions tab -> identify which user holds the saved draft and have them Submit or Cancel |
| What the User or Admin SeesDelegator clicks notification link and gets blocked | Underlying Workday MechanismTask was delegated via Manage Delegation Settings with Retain Access to Delegated Tasks within My Tasks unchecked | What to Check on Full Process RecordProcess tab -> Person column lists only the delegate; All Actions shows the delegate as Awaiting |
| What the User or Admin SeesNew hire / internal transfer gets blocked on Onboarding link | Underlying Workday MechanismSigned into external Candidate Home session while clicking an internal Worker task link (or pre-hire step gated by effective date) | What to Check on Full Process RecordConfirm which portal URL and account type the person used, and compare event effective date vs. step conditions |
| What the User or Admin SeesEvent sits at ‘Waiting on Initiator’ indefinitely | Underlying Workday MechanismStarter clicked Save for Later on the Initiation step, or an approver clicked Send Back to Initiation | What to Check on Full Process RecordProcess tab -> check whether row 1 (Initiation) is still open or whether Comments shows a Send Back reason |
| What the User or Admin SeesInitiator sees the sent-back event in history, cannot open task | Underlying Workday MechanismInitiator lost the constrained role they held at initiation, or the Business Process Security Policy omits Initiator on that step | What to Check on Full Process RecordCompare initiator’s current role assignments against Edit Business Process Security Policy step permissions |
Step 1: Inspect the Full Process Record First
With Modify access on the Business Process Administration domain (or View All on the specific Business Process Security Policy), locate the business process instance—either from the target worker’s Worker History, or by running Business Process Transactions Awaiting Action / Business Process Transactions of Type Awaiting Action.
Open the event’s related actions menu and select Business Process > Full Process Record, then check three tabs:
- Process tab: Check the Status column on the active row, the Person (Up to 5) column, and the All Persons count. A completed step displays
1in All Persons; an unassigned step displays0(meaning the target role is vacant and needs reassigning an awaiting action); an active shared role displays the total count of eligible assignees. Check the For column to see if an admin or peer already reassigned the task away from the person clicking the link. - Comments tab: Look for a Send Back entry. When a reviewer clicks Send Back to return an event to a prior Action step or the Initiation step, Workday logs the comment and timestamps the return.
- All Actions tab: Review the By column and Event Record Moment to see the exact chronological chain of initiation, Save for Later, delegation, or reassignment events.
Step 2: Resolve ‘This Task Is Not Available’ Without Breaking the Event
Once the Full Process Record reveals why the link failed, apply the matching fix:
- Colleague completed or claimed the step via
Save for Later: Have the user navigate directly to My Tasks inside Workday rather than clicking old email URLs, and check Archive in My Tasks if they already submitted it. If a teammate clicked Save for Later and went on leave (which strips the task from all other role members and disables Skip This Task), an administrator can use Reassign Steps or Cancel depending on whether entered draft values are needed. - Delegation hid the task from the delegator: Under Manage Delegation Settings, leaving Retain Access to Delegated Tasks within My Tasks unchecked removes the delegator from the Process tab’s Person list and routes the item exclusively to the delegate. Either have the delegate complete the step or update the delegation rule.
- Candidate vs. Worker session collision: During recruiting-to-hire transitions, candidates frequently have an active Candidate Home browser tab open when their new employee SSO credentials arrive. Have them sign out completely, open a clean browser session on the internal tenant sign-in page, and open My Tasks directly from the top navigation bar instead of an email deep link.
- Broken
Generate DocumentsRun-As security: If a business process hangs on a Generate Documents step and the intended recipient has nothing in My Tasks, check the step’s Run As User configuration. An Integration System User configured as Run As User must belong to an unconstrained ISSG secured to the Document Generation Results domain and hold View All permission on the parent Business Process Security Policy; otherwise Workday fails to generate the document and leaves the step stranded.
Step 3: Clear Steps Stuck on ‘Waiting on Initiator’
When a transaction stalls on the initiator, distinguish an abandoned draft from a Send Back permission trap:
# Classic Send Back security trap:
1. HR Coordinator initiates "Change Job" for Worker A in Supervisory Org East
2. Next week, HR Coordinator transfers to Supervisory Org West (losing constrained East role)
3. Approver clicks "Send Back" -> returns event to Initiation / Action step
4. Event sits "Waiting on Initiator", and HR Coordinator gets "This task is not available"# Clean resolution:
1. Admin checks Full Process Record -> Process tab confirms step is awaiting former coordinator
2. For one-off event: Admin runs Business Process > Reassign Steps to current East HR Coordinator (or Cancels draft)
3. For systemic BP step security gaps: Edit Business Process Security Policy -> grant Initiator / target group step access -> Activate Pending Security Policy ChangesUnsubmitted Initiation steps cannot always be reassigned
Workday allows administrators to reassign active workflow steps after initiation via Reassign / Reassign Steps, whereas an Initiation step that was merely saved via Save for Later and never submitted has not yet kicked off downstream workflow routing. If the original drafter left the company or abandoned an unsubmitted Initiation draft, cancel the draft event (see when to rescind, cancel, or correct a business process) and initiate a clean transaction.
If the step stalling the workflow is a custom Action, Review Documents, or Questionnaire step configured to route to the Initiator security group—and every initiator hits This task is not available—open Edit Business Process Security Policy for that business process type (see domain vs. business process security policies). Verify that Initiator (or the appropriate role-based security group) is explicitly listed in the Action / step permission grid, ensure no routing restriction on the step excludes them, and run Activate Pending Security Policy Changes.
How to Verify the Fix Worked
To prove the step is genuinely unblocked—not just visible in an admin report—check two things:
- On Full Process Record > Process, confirm Status is Awaiting Action, All Persons is at least
1, and the expected worker appears in Person (Up to 5). - In Sandbox or Implementation, proxy as that assignee (or have the user open My Tasks directly in Production without using the old email link) and verify the task form opens with active Submit / Approve buttons. For broader stuck-queue cleanup, pair this check with our business process awaiting action troubleshooting guide.
When you connect a tenant in Kiweely Vine, you can paste a stuck event name or worker ID and let the agent inspect the Full Process Record, step conditions, assignee role history, and Business Process Security Policy together—explaining immediately whether the step is locked by Save for Later, missing Initiator step permissions, or waiting on a vacant role, and testing workflow fixes in a visible, stoppable browser across personas.
Frequently asked questions
Why do I get 'This task is not available' when clicking a Workday email notification link?
Email links point to a specific step assignment ID. If another member of the shared role already completed the step, clicked Save for Later, or reassigned the step, or if you are signed into a Candidate account instead of your internal Worker account, Workday blocks the stale link with This task is not available.
What happens to other recipients in My Tasks when someone clicks Save for Later?
When one recipient clicks Save for Later on a business process step, Workday immediately removes that My Tasks item from all other recipients assigned to the role so two people cannot edit the step simultaneously.
What does Waiting on Initiator mean on a Workday business process?
Either the person who started the event clicked Save for Later on the Initiation step without clicking Submit, or a downstream approver used Send Back to return the event to the Initiation step for correction.
Why cannot the original initiator open a step that was sent back to them?
If the initiator changed supervisory organizations or lost their constrained role assignment after starting the event, or if the Business Process Security Policy lacks permission for the Initiator or their current security group on that step, Workday routes the step back but blocks them from acting on it.