test API flow error: "Problem deleting proxy for flow, Not able to retrieve proxy resource for tena

Kirill Kuchumov

I have built simple API flow with just one API CRS610MI.Add.

When I test API within API flow it works file.

When I test it in "ION API > Infor API flows > Documentation > Try it out" it works fine.

However when I test API flow itself

M3 API is executed, new customer is added to CRS610, but I get this error

Does anyone know why?

Is there something missing?

Thanks,

Kirill

Find more posts tagged with

General Discussions

Accepted answers

unknown

I can confirm this is a product issue that has been already addressed. A fix is expected in the 2022.07 update.

All comments

David TOLLET

Hi Kirill,

I recently also faced the same issue when beginning to use API flows. I thought I was doing something wrong on my side ! I Managed to fix this by creating a brand new API flow and activated it.

Maybe you should try creating an Infor Support Portal incident, seems to be buggy somewhere.

Regards,

David.

unknown

Can you please try

a.) deactivate followed by reactivate (If the deactivate gives any error, you may ignore that and refresh)

b.) Redo the same flow as a fresh attempt but with a different name and endpoint, activate and try?

If either of the above fixes the issue, this is most likely a defect.

gsingh

We had the same issues a few weeks back and have an incident open with Infor. It seems it was working better but possibly around the time the api step output column was removed (not sure) we also started seeing some reliability issues like this. Creation of a flow is OK , but re-activating gives this duplicate error. We can create a new one with a different context / resource name but that is not practical of course. We can delete the flow but the issue is the endpoint is remaining.

Infor recommended some steps to delete the endpoint but that is not working or is intermittent. I did not look at this for a few weeks but tried again today and cannot delete the endpoints still so have asked them to check further.

I am not sure how many use this but we are having issues with the reliability and also how to use them to get output as the documentation is not that useful. We need to test more however so may have more success.

unknown

// It seems it was working better but possibly around the time the api step output column was removed (not sure)// I want to clarify that there is no relationship whatsoever between api output step and this issue.
API Step output design has not changed since the product release. (It was differently designed during the beta phase and had to be changed for external constraints). You also indicated 'not sure'; Just wanted to confirm that, indeed it's a misleading reference.

unknown

I can confirm this is a product issue that has been already addressed. A fix is expected in the 2022.07 update.

gsingh

Thanks Vignesh for confirming this will be fixed and clarifying re the output field change. Will do some more testing next week after the update.

Kirill Kuchumov

Thanks Vignesh.

I did that bunch of times, same error happens.

Looks like the problem is on Infor side.

Kirill Kuchumov

Thanks Gurmaj!

Copyright © 2025 Infor. All rights reserved.