Json No Code and Json No Code oAuth Connector - Add response details

paulmorrisey

These connectors both return errors that start with "Domo is ready but…" in the dataset history which provide very little detail into the error that actually occurred.

I'm not sure but from examples I've seen it seems like this might be a generic set of messages based on the HTTP status returned.

I appreciate that Domo can't anticipate the interesting ways ever API developer might decide to categorize the response but I think it would be valuable when an endpoint sends a response to actually include that information.

I have to resort to using writing Python so I can actual inspect endpoint response to get a useful diagnostic response and then I'm still only guessing it's the same response that the connector got.

This problem also occurs in the pagination, parsing setups. You can get a generic "Something went wrong" error which really doesn't do much to inform what happened. Again the actual response is often useful.

I had one connector where the endpoint in python testing was responding with "you must provide x, y, z" because it didn't have a default setting for the page or page size parameter. I found you could work around that by setting it statically injecting those parameters on the data selection step with default value and then inputting them again in the pagination step which does seem to then let the pagination step retrieve the sample, and then start paging from there so you can move on the parsing section.

I think being a "No Code" solution means many of users won't be able to resolve these issues and it would be a great enhancement to provide some detail so even if they have to reach out to someone else they have diagnostic responses at all.