Share
ReportHello,
I added the x-ms-pageable property to one of GET actions in my in-development connector (in preprod environment), and then enabled Pagination.
With Pagination enabled, this action failed due to "Access token is empty" error. Without Pagination, this action worked fine.
So, I believe this action failed in a subsequent call.
This API supports next link as well as "value" in a response is an array so it should be able to work with Pagination.
What would be a potential cause for losing access token in a subsequent call?
I added the x-ms-pageable property to one of GET actions in my in-development connector (in preprod environment), and then enabled Pagination.
With Pagination enabled, this action failed due to "Access token is empty" error. Without Pagination, this action worked fine.
So, I believe this action failed in a subsequent call.
This API supports next link as well as "value" in a response is an array so it should be able to work with Pagination.
What would be a potential cause for losing access token in a subsequent call?
This error wasn't logged in my backend service so I believe this error was thrown by Power Automate before hitting the backend service.
Thanks in advance.
Thanks in advance.
Categories:
I have the same question (0)
All responses (
Answers (
229
