Troubleshooting
Request cannot move forward
Resolve a blocked submission, missing approver, out-of-date request, unavailable decision, or full paid position limit.
Updated August 10, 2026
Overview
Find where the request stopped: before submission, at an approval stage, during final approval, or after it closed. The request page usually names the requirement that no longer holds.
Do not create a duplicate request until you understand the existing one.
Submission is blocked
Check:
- Every required proposed value is complete.
- Effective dates are valid and the position is not active before required information begins.
- No conflicting request is active for the position.
- Every required stage in the selected request-type workflow has an eligible approver other than the requester.
- The requester has Submit position requests and position access.
- A new active position has an unreserved paid position place.
- Every required named file box contains its own file; an additional file does not satisfy it.
- Any blank form offered by a named field is ready to download.
- The request type has an available Reason group with at least one available choice, a Reason is selected, and sensitive Justification is present when that workflow requires it.
Correct the named issue, review the request again, and submit.
No eligible approver
The requester cannot decide their own request. If a required stage has no other eligible approver, an approval administrator must correct stage or approver setup before submission.
Review:
- The request type and its workflow’s stage availability.
- Department approvers for those exact request-type stages.
- Active user memberships.
- Role and department access.
- Requester’s identity.
- The workflow’s Workflow defaults, including its Complete through selection.
- For Position change only, any later stages assigned to the changed fields.
Do not grant broad access solely to bypass one request. Configure the intended approver responsibility.
Request is waiting at a stage
Open the stage detail and confirm:
- The stage is active.
- At least one selected approver is active.
- The request appears in My approvals > Ready now for the intended approver.
- A prior decision did not already move or close it.
- Notification delivery is not being mistaken for assignment status.
The request remains available in FTE Tree even if an email is delayed.
A file is blocking approval
Approval and an administrative approve override wait until every submitted file passes its safety check. A pending check may finish without any change from the requester. A failed, infected, unsupported, or missing check cannot be bypassed.
Open the request to identify the affected named or additional file within your access. An approval administrator can also find overdue or unavailable checks under Administrative approvals > Needs attention, but that list does not show protected filenames. Denial remains available when the request should end. If corrected evidence is needed later, the requester provides it in a complete new request.
Approver cannot decide
The person may be able to view the request without being assigned to the current stage. Only an approver assigned to the current stage can use the normal decision action.
Also check whether another eligible approver already completed the stage, the request closed, or the person is viewing a different organization. One eligible decision resolves the stage, so the other active assignments no longer need action.
An approval administrator can record a response for another approver when appropriate and authorized. Use an override only for an exceptional administrative decision.
Request was invalidated
An invalidated status on a retained request means a system safety rule closed that submitted attempt. Calculation updates do not invalidate an active request.
Compare the retained submitted values with the current approved position. If the change is still needed, enter the complete current proposal normally and create a new request. The invalidated request stays unchanged for history.
Denied or invalidated request cannot be edited
A denied or invalidated request is closed and read-only. Review the denial reason or invalidation explanation, then use the normal Position editor and request process when the organization still wants the change. Earlier values, files, decisions, and approvals are not copied.
New-position approval cannot finish
Review:
- The request still holds its reserved paid position place.
- Required active-position values remain valid.
- Department and Job code choices are valid for each date.
- The request is still active.
A request that already reserved a paid position can finish even if a later subscription change puts the organization over its current paid position count.
What to record
Before asking for help, note:
- Request number and position number.
- Current status and stage.
- Exact visible message.
- Intended action.
- Approximate time.
- Whether setup, access, or the position changed after submission.
Share this with the organization’s approval administrator. Contact Support when the visible state conflicts with current setup and access.