R - Domo API SDK (rdomo) - Working??

CityExplorer

Hi,

My colleagues and I, from various departments including Research and Accounting, were surprised when the Domo API stopped responding last Tuesday. Initially, we suspected it might be an issue with our IT Department, but they promptly confirmed that they hadn't blocked any API calls and had checked their firewall settings.

The error we are getting was simple time out using:

data ← domo$ds_get("")
Error in if (time_since < 50) { : missing value where TRUE/FALSE needed

We use Domo API for multiple workflow around the company. Could you help us?

Thank you

CityExplorer

Hi @ArborRose

I finally resolved the issue with RDomo and the Domo API. The problem was due to a change in Domo's AWS server configuration by Domo HQ. My IT team has now applied the new configuration. Everything back normal and I have just bunch delays for me to deal just before the Holidays🙄.

ArborRose

Some suggestions:

• Check API Rate limits
• Verify the query itself
• Check API Authentication. Make sure the token has not expired. Test with a simple GET.
• Check if there's too much data being fetched. Maybe try a small set as a test.
• Check with IT to make sure no firewall settings changed, blocking the call

CityExplorer

Hi @ArborRose ,

Thank you for the quick reply.

• Check API Rate limits ✅ (Check)

• Verify the query itself✅ (Check)

• Check API Authentication. Make sure the token has not expired. Test with a simple GET. ✅ (Check)

• Check if there's too much data being fetched. Maybe try a small set as a test.✅ (Verify with 5 rows dataset)

• Check with IT to make sure no firewall settings changed, blocking the call ✅ (Verify with IT security team. The first thing I did when I saw this problem)

What makes this issue so strange is that there's no response from the Domo API. Typically, any misconfiguration or rate limit would return an error, but the worse to be completely ghosted by the API server because you don't where is the problem.

Do you able to use Domo API with RDomo?

ArborRose

I don't use the API with R-Domo. I use other connectors via Python, etc.

Based on your "check list", it looks like you can communicate with a small dataset of five rows. That makes me lean toward thinking the size of the dataset may be an issue. You might try gradually upping that size and retest.

I've had an issue in Jupyter / Python where I can confirm the API has finished sending the data, but my data frame has not completed receiving and storing it before a timeout. This leaves me with an empty dataset. To solve this I put a retry counter to force the code to give it extra time for the delivery. I wonder if you are hitting something similar.

CityExplorer

Hi @ArborRose

I finally resolved the issue with RDomo and the Domo API. The problem was due to a change in Domo's AWS server configuration by Domo HQ. My IT team has now applied the new configuration. Everything back normal and I have just bunch delays for me to deal just before the Holidays🙄.