Toggl connection stopped working - getting "Integromat account error: 418"

So your service status page doesn’t mention the Toggl outage at all. So that’s not helpful - and makes it seem like you’re not being honest about what’s working and what’s not.

It’s been over a week since Toggl stopped working - and Make hasn’t offered a work around, or a timeline for addressing the problem?

Service disruptions and updates have to be manually added to the status page, only the stats/graphs sections are automated.

1 Like

Perhaps I’m not understanding your reply or the purpose of Make’s status page. The fact that the status appears to have no issues currently, despite a known (and persistent) outage for an entire app, doesn’t match the reality for Make’s customers. I understand having delays in the data if specific pieces need to be manually updated, but seems reasonable to expect this would be there given that the issue began over a week ago. At present, I’m not understanding how the information currently on the status page is helpful in our current situation (or how it answers @zck 's questions). Again: I may be (am likely) missing something, and would appreciate any clarification you can provide!

Similar to @zck, I was trying Make as a solution to integrate across several platforms. I was impressed with its ability when I got the first scenario running a couple of weeks ago, but then it abruptly stopped last week. It appears as though Toggl’s API change was scheduled and had been communicated several months prior, so the present situation seems avoidable entirely.

In the short term, it would be incredibly helpful to know:

    1. a recommended workaround for the current situation, if one is known
    1. the current status / progress of a resolution (in progress, in review, on deck, etc)
    1. a timeline for resolving the issue at hand

In the longer term, it would be helpful to have a better understanding of:

    1. how frequently individual outages for specific apps occur, and the typical speed at which they’re fixed
    1. how API changes (on the app side) are typically handled (proactively?) to avoid issues in the first place

Big picture: Currently, you have customers who are impacted by an outage lasting more than a week, that isn’t listed on the status page, and without a known timeline or transparent communication regarding the status of the resolution. It’s unfortunately difficult to picture transferring significant operational processes over to Make given all of this. I’m hoping this is seen as a serious issue by folks at Make, and is addressed accordingly.

6 Likes

OK so - Make’s customer service just totally ghosted us all when we pointed out that they’re having an outage for weeks and no indication of when it’ll be fixed. Definitely not going to recommend this for my company

Product failures + Bad customer service => no business.

2 Likes

Hello everyone @here

Once again, we are very sorry for the disruption, trouble, and frustration this has caused.

Just to clarify, our status page is reserved for updates that affect large portions of our users. Since this particular issue does not fall into that category, it is not featured there.

I also wanted to let you know that our dev team is actively working on releasing a fix for this. As soon as I learn about any updates, I will make sure to post them here. If you prefer to get notified in your inbox, please open a ticket with us, and our support team will keep you informed about the progress.

Thank you very much for your patience and understanding.

1 Like

No worries Michaela - I’ve moved on. Please consider adding status updates for the actual functionality your product says it offers.

Hi Michaela - thank you for the reply, and the additional information that it’s being actively worked on!

2 Likes

Hello everyone @here

I just wanted to let you know that the dev team implemented a fix to this issue a moment ago. Could you please test creating a new connection and confirm if everything is working for you?

Once again, we apologize for any inconvenience this may have caused you.
Thank you for your patience and collaboration :pray:

2 Likes

@Michaela all good - connection tested and well received! I had success connecting to the webhook - I appreciate it :pray:

Now need to go back a while to make sure the modules still work. Thank you Make for solving this problem!

1 Like

@Michaela Thank you for circling back and letting us know!! I wouldn’t have known to check today otherwise, and… The connection is back up and running, and is better than ever :tada: :raised_hands:
(For anyone who hasn’t tried if out yet, the Toggl API V9 has Client and Project Names rather than just IDs, and can filter Time Entries based on Client!)

If there’s an opportunity for feedback (to thank you for letting us know to check the connections! and about the status page in general), please let us know? Even hearing about the active work status last week was a huge help in determining an interim course of action that worked for my business.

Again: much gratitude to you and the dev team :pray: I hope you have a wonderful rest of the day!

1 Like

Hello @Chris_Harvey @grace_pf ,

Thanks a lot for letting us know that everything’s working for you. We also definitely appreciate the extra tips and information you shared for the rest of the community!

If you ever have any feedback you’d like to share, feel free to use this form. The very last option in the dropdown menu allows you to leave comments.

Thanks again for your patience and collaboration throughout this process. :pray:

1 Like

Thanks for upgrading the Toggl API to V9.

I have a problem when downloading a report to either a CSV or XLSX file. The files aren’t recognized by Excel or Google Drive because both file names have an underscore at the end.

I can get it to work by using the map and changing to a different file name.

image