Hey friends,
Thanks a ton for all of the community contributions, I have answered many questions from searching. This time I couldn’t find anything similar to what I’m encountering.
I have a WIP scenario in which I am pulling data from a 3rd party API. The user must first run through an OAuth flow to authorize my application to access their information, and successful authorization POST to a primary scenario I have that obtains an access token and does CRSF validation. When that scenario for authorization and access succeeds, it fires a request to a webhook in the current (secondary) scenario.
This secondary scenario performs the requests for information from the third party API, but the internal permissions of the user may or may not allow certain API endpoints. In the first route of the scenario, I request data from one set of API endpoints, however if the user’s internal permission does not allow that data to be exposed, the scenario fails with a HTTP 403.
I’ve reviewed the options for error handling and tried an Ignore, Break, and Resume; Ignore continues with many operations asking the API for details and receiving 403 before proceeding. Break will retry which is not a good option since the user internal permissions won’t change. Resume gives me a chance to replace the errant data, but in this case not applicable. I’d like for the module and ultimately the route that receives the 403 to cease execution, and for the remaining secondary route to continue until scenario completion. Is there a way to catch the 403 and proceed?
If I can’t do this, I’ll have to break this secondary route into another scenario, not a deal breaker but slightly annoying for historical review and tracing in customer support scenarios.
blueprint.json (127.2 KB)
