ConfigBot For Dayforce - Self Trouble Shooting Guide
This guide will help you understand the common errors encountered while using ConfigBot and how to troubleshoot them
Login Issue:
If you are facing login issues despite entering correct login details, there are a few ways to troubleshoot them
A. Click the Forgot Password option. Enter your email address, and a password reset link will be sent to your email. Use this link to reset your password and log in again.
Alternatively, you can ask your company administrator to reset your password.
B. In another case, if you are able to log in but receive an error indicating that the MFA code is incorrect, delete the previously scanned QR code from your authenticator app and scan the QR code again to set up a new MFA.
Alternatively, you can ask your company administrator to reset the MFA for you.
If this does not resolve your login issue, you can always reach out to us anytime via the following email addresses:
Common Errors While Execution.
A. Wrong password, username, or company ID
When you encounter this error in the logs and are unable to log in, it indicates an issue with the instance details, such as an incorrect company ID, username, or password. Verify these details, then request a reprocess and rerun the iteration with the correct information.
B. Error from Google
When you see an error from Google, it means that in one of the objects the data in a workbook cell has exceeded 50,000 characters. This will not stop the execution—the data will still be available, and the bot will continue to generate or automate the other objects.
C. Instance on update, 500 error
When you see errors in the logs such as “step instance” or a 500 error, it means that the Dayforce instance went into an update or optimization during execution. During this time, the bot will stop generating or automating the workbook. Once the Dayforce instance is back online, you can retrigger the execution. The bot will resume from the object it was last working on.
D. Step Instance is slow, Unexpected Error Occurred Contact Support
When you see errors in the logs such as “step instance is slow” or “unexpected error occurred,” this may happen for several reasons. One common reason is multiple logins while the bot is running. If you are working in the instance at the same time, the bot may attempt to log in multiple times, and after several attempts, it can result in a step instance slow error. In this case, you can retrigger the execution, and the bot will continue from the object where it left off.
Another reason for an unexpected error could be that your account requires a password reset or dayforce went under maintenance or your account has MFA enabled. In rare cases, the issue may be due to a code-related error. If this happens, you can always email us and share the tracking IDs, or send them through the chat box available on your dashboard.
E. Data Errors,
Sometimes, the execution shows an error when data is missing in mandatory fields or when the data is not present in the instance during automation or migration. In this case, the logs will highlight the object name and the missing field. The bot will skip that object and continue automation and migration for the rest. You can add the correct data and rerun the execution, or share the tracking ID with us, and we will assist you.
By following these troubleshooting steps, most common ConfigBot errors can be quickly identified and resolved, ensuring smooth automation and migration. You can also connect with us anytime via chat, email, or calls for further assistance.
Updated on: 01/23/2026
Thank you!