Introduction
The timesheet submission status feature in Roubler helps track and troubleshoot timesheets through each stage of submission. Occasionally, timesheets may get stuck in the "submitting" status if there’s no clear response from the payroll system due to a system error or a delay. This guide explains how the submission status works, the new reset feature, and steps to troubleshoot submission issues effectively.
How Timesheet Submission Status Works
The submission status indicates where each timesheet is in the processing cycle. When submitting timesheets in bulk or individually, the status shows whether they’ve been successfully processed, are awaiting action, or require troubleshooting.
Status Types and Reset Options:
- Committed: Timesheets are ready and set for submission.
- Submitting: Timesheets are in the process of being sent to the payroll system but have not yet completed.
- Stuck in Submitting: If the system encounters an issue (e.g., a crash or a delay in the API response), timesheets may remain in the “submitting” state.
- Resetting to Committed: After one hour, if no response (success or error) is received from, you can manually cancel and revert the timesheet status back to “Committed” using the Cancel button.
Please note this is non-blocking so you can safely navigate away from the page and come back later.
Example Scenarios:
- If Roubler encounters a delay during submission, the timesheet may not fully process. After 15 minutes, the Cancel button becomes available, allowing you to manually reset the timesheet back to “Committed.”
- Timesheets only automatically revert to “Committed” if a failure message or error response is returned. If no response is received within the hour, the system keeps timesheets in the “submitting” status until manually reset.
How to Troubleshoot Stuck Timesheets
If a timesheet is stuck in “submitting” status, follow these steps to troubleshoot the issue:
-
Wait for 15 Minutes:
- After an hour, timesheets still in “submitting” status can be reset manually. The Cancel button will appear, allowing you to roll back the timesheet to “Committed.”
-
Check the Status in the pay engine:
- Before resubmitting confirm whether any part of the submission went through. Since the system couldn’t confirm the result, it’s essential to verify to avoid duplicate entries.
-
Resubmit After Checking in the pay engine:
- Once you’ve confirmed that no submission went through, try resubmitting one timesheet first to ensure it processes successfully. If that goes through smoothly, proceed with the remaining timesheets.
-
Handle Error Messages:
- If an error returns, the system will automatically revert the timesheet to “Committed,” allowing you to troubleshoot and resubmit.
-
Using the Cancel Button for Manual Reset:
- If no response was received from the pay engine, and the timesheet remains in “submitting” after 15 minutes, use the Cancel button to manually reset it to “Committed.”
Frequently Asked Questions
Q: What should I do if my timesheets remain in “submitting” for more than an hour?
A: After 15 minutes, the Cancel button will become available, allowing you to reset the timesheet to “Committed.” Check the pay engine first, then attempt to resubmit the timesheets individually.
Q: When will timesheets automatically revert to “Committed”?
A: Timesheets will automatically revert if an error message or failure response is received. If there’s no response at all, you’ll need to use the Cancel button after the hour has elapsed.
Q: How do I prevent duplicates when resubmitting timesheets?
A: Before resubmitting, visit the pay engine to confirm the status of the timesheets. Start by resubmitting one timesheet to test, and if successful, proceed with the others.
Q: Is the reset feature available immediately?
A: The Cancel button for resetting to “Committed” becomes available after the timesheet remains in “submitting” status for 15 minutes without a response.
By understanding how the timesheet submission status works and following these troubleshooting steps, you can ensure smooth processing and manage any issues that arise effectively. Please contact support if you have further questions or encounter persistent issues.
Comments
0 comments
Article is closed for comments.