-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error The following error occurred: [object Response]
#94
Comments
@digdert I'm looking into it now. I'll let you know what I find. |
@digdert I tried a couple of transfers between both tools and didn't run into this issue. I made sure to review the Clockify and Toggl API docs to verify that nothing else may have changed. Are you able to transfer any time entries over, or does it break immediately? |
@mikerourke here is an screen record Does date format important? |
Hey @digdert, I apologize for the delayed response, I've had a hectic week. Are you familiar with using the browser DevTools? I think I can get a better idea of the error if I can see the failing network request details. |
I used it several times again, and I completely moved to Clockify now! I assume this happened due to a character in entries name or several tweaks, because I enabled Clockify free trial and then I could IMPORT entries from Toggl officially in Clockify. I used it to transfer several entries, and after that, Anything was okay. Also, I had several entries with NO PROJECT assigned (-> clockify import feature miss understood this entries too) My entries contained dash
|
I'm glad to hear you transferred everything over! I'll try creating a few test entries with those characters to see if I can reproduce and address the issue going forward. Thanks for following up on the issue! |
Hi there
I started transfering from toggl to clockify
all transfer sections done seccufully but only time-enteries rises an error
The following error occurred: [object Response]
I tried several times but nothing happend
thanks in advance
The text was updated successfully, but these errors were encountered: