We daily receive support requests reporting the “Your automation has failed due to a resource not being found” error message received after the app runs.
As far as I know, this error message is sent when the app is not enabled to operate in that particular workspace. The problem can be fixed by enabling the app in that or all workspaces.
So I’m here to ask the monday devs a couple of improvements:
Even if an app is not enabled in a workspace, it can be added and set up, without any warning. Only after the user runs it, he get the error.
If you still want to show the app in the marketplace despite not being enabled in the workspace, please at least add a warning saying that permissions have to been changed.
The error message is enigmatic and most users don’t know what to do. Please change it into something more meaningful, like “Your automation failed because [APP_NAME] is not enabled in the workspace”.
Finally, I noticed that now the action “internal name” is displayed in the activity log (see “Send to General Caster (formula - no triggerColumnId)” label in the screenshot above).
This is an internal label not meant to be shown to the user.
My experience is that the even when the app isn’t enabled in a workspace, it still sends the payloads to our back ends, with a token. The issue pops up when the token fails to retrieve the requested data (it just doesn’t get returned, no GraphQL errors) because its not granted access to the workspace.
The resource not found shows up when we return a 404, so if your code returns a 404 if you can’t find something (say something like read item 123123123, and 123123123 isn’t returned by the query, you return a 404 not found) then it will show “resource not being found”.
In this case, what I do is return an error response saying there is a permission issue, check the recipe creator is a board owner and the app has permission to the workspace. This shows up in the integration log specifically saying this.
Thank you, @codyfrisch, for your feedback.
We return proper HTTP error codes, so I guess this is the case.
Error messages must be improved on monday’s side anyway.
I don’t disagree.
If you include the Error handling in the response body, and fail to include
runtimeErrorDescription then it will default to the default 404 error message there (assuming you returned a 404). If you do provide a meaningful
runtimeErrorDescription then your custom message gets displayed instead.
Thank you for this!
I have changed this into a request topic. You can vote for it at the top!
Thanks for your feedback - we’ve passed it on to the team. They’ve already deployed a fix for the action name issue, and we will keep you all updated on the others
I hope it’s not related to the fix…
I am a functional user who has built a lot of automations and general caster integrations. Today I loaded some data into a complex board and some, but not all, integrations failed “Due to a resource not being found”. I checked the integrations and the columns in the formula still exist on the board and the target columns still exist on the board. These processes used to run without issue, but i have not run them since early January. My “app” is General Caster and it’s running fine on some integrations. Sorry for not being more technical, but can someone provide some advice about how to debug this?
@mdalzell By chance are you seeing errors in one workspace but not another?
Yes, it seems to be isolated to my workspace. I am not seeing the same issues in my colleague’s integration activity logs. What are you thinking might be the issue?
I am noticing some different General Caster failures from 1/29/24 in another workspace, but I am thinking they can be attributed to Monday’s platform issues this week. Those are “This automation failed due to an issue with an app you installed. Contact the app developer to fix this.”
Do you think that Monday could still be having platform issues? Is it possible our environment doesn’t have enough computing resources dedicated which would make my integrations fail for lack of resources/horsepower? I just ran another form through the same process with the same data and most, but not all, the integrations ran fine. This is very odd.
That is odd, I was going to say if the issue is isolated to a specific workspace, check this article out: https://support.monday.com/hc/en-us/articles/8576973881362-Managing-app-access-on-your-account
Its possible somebody inadvertently restricted it, and did not include or removed your workspace from allowed workspaces.
Basically an app needs access to any workspace it runs in (or the whole account) and if its looking at mirror columns, the boards being mirrored may also need to be in workspaces it has access to.
Thank you Cody. I appreciate the assist. Everything ran fine when I sent the data through a second time. A head scratcher.