# API Enrichment error handling

**URL:** <https://community.parabola.io/t/api-enrichment-error-handling/122>\
**Category:** Feature Requests\
**Tags:** Integration\
**Created:** [March 16, 2020, 10:15pm UTC](https://community.parabola.io/t/api-enrichment-error-handling/122 "2020-03-16T22:15:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Kinsel](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@Matt\_Kinsel](https://community.parabola.io/u/Matt_Kinsel)\
**Post date:** [March 16, 2020, 10:15pm UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/1 "2020-03-16T22:15:05Z")

</div>

1. What is your feature/integration request?  
Allow the API Enrichment step to continue to process rows after an error, and log the errors in the table so that they can be used in later steps.

2. What problem would this feature/integration solve?  
Integrating with this API that uses a 403 error if the request cannot be completed (due to internal filtering, impossible to know beforehand and happens about 50% of the time): [https://apidocs.straticsnetworks.com/reference#single-rvm-drop](https://apidocs.straticsnetworks.com/reference#single-rvm-drop)

3. How do you solve/workaround this problem today?  
Will try relaying the requests through Integromat or [pipedream.com](http://pipedream.com), but operation limits compared to the volume Parabola can handle may make this much more expensive or impossible.

---

<div class="post-metadata">

**Author:** ![jim](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jim](https://community.parabola.io/u/jim)\
**Post date:** [March 31, 2021, 8:03am UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/2 "2021-03-31T08:03:32Z")

</div>

Is there any progress on error handling? It’s much requested.

Is there a roadmap anywhere for the product?

---

<div class="post-metadata">

**Author:** ![Adam\_R](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/adam_r/32/2207_2.png) [@Adam\_R](https://community.parabola.io/u/Adam_R)\
**Post date:** [March 31, 2021, 11:57pm UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/3 "2021-03-31T23:57:50Z")

</div>

Hi Jim and Matt 👋

Wanted to let you know you know that this is on our roadmap and we will be sure to update this post as soon as we have an update to share!

While we do not have a public roadmap currently available, we are certainly open to creating one. What information do you think would be most helpful/ valuable for us to include?

---

<div class="post-metadata">

**Author:** ![jim](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jim](https://community.parabola.io/u/jim)\
**Post date:** [June 2, 2021, 1:45pm UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/4 "2021-06-02T13:45:30Z")

</div>

Hi @Adam_R ,

Working on a flow today that reminded me about error handling. Is there an update? I’ve got a flow with 30k records I need to update and although I’ll be batching them up errors do occur.

Error handling has been much discussed in the community, and I’m getting the sense that Parabola’s focus is moving more towards shopify / ecomm rather than as an integration platform. It may be just your new messaging. Would be nice to hear some more on the direction of the product.

re: the roadmap a simple kanban approach would probably work with some expectations set on timescales.

Hope that helps - Jim

---

<div class="post-metadata">

**Author:** ![Adam\_R](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/adam_r/32/2207_2.png) [@Adam\_R](https://community.parabola.io/u/Adam_R)\
**Post date:** [June 2, 2021, 7:37pm UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/5 "2021-06-02T19:37:46Z")

</div>

Thanks for your note @jim! Totally understand the desire to check out a public roadmap – your request has been passed on to the team.

Error handling is on our list and has been discussed internally. We will continue to consider this area in upcoming cycles. Appreciate your patience, and always happy to help troubleshoot any errors at [support@parabola.io](mailto:support@parabola.io).

---

<div class="post-metadata">

**Author:** ![Adam\_R](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/adam_r/32/2207_2.png) [@Adam\_R](https://community.parabola.io/u/Adam_R)\
**Post date:** [March 16, 2022, 2:49am UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/6 "2022-03-16T02:49:33Z")

</div>

Hey @jim @Matt_Kinsel –

Wanted to share the good news! We just released new error handling functionality in our “Enrich with an API” and “Send to an API” steps. Feel free to check out [this post](https://community.parabola.io/t/new-error-handling-on-api-steps/2308) for the full announcement – particularly curious to hear your feedback!

---

<div class="post-metadata">

**Author:** ![Adam\_R](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/adam_r/32/2207_2.png) [@Adam\_R](https://community.parabola.io/u/Adam_R)\
**Post date:** [March 16, 2022, 3:01am UTC](https://community.parabola.io/t/api-enrichment-error-handling/122/7 "2022-03-16T03:01:34Z")

</div>


