We’re currently implementing a somewhat tricky web service connector, and we’ve encountered an issue we’d appreciate your insights on.
In our setup, account aggregation uses a different endpoint than provisioning operations (i.e., test connection, add entitlement, create, and update account).
So far:
Account aggregation and test connection operations are working successfully.
However, provisioning operations remain stuck in the pending state.
When we cancel these pending operations and inspect the Account Activity via search, we can confirm that the generated provisioning attributes are correct and behave as expected when tested directly in Postman.
We’re a bit puzzled by this behavior and would greatly appreciate any guidance or suggestions you might have.
Thank you for your insight — that was indeed the root cause of the provisioning operations being stuck in the pending state.
However, we’re now facing a related issue: the account attribute defined as the Account ID is not being included in the generated provisioning plan. While assigning the Account ID to a different attribute might be a workaround, we’d like to better understand what could be causing this behavior.
Any guidance or clarification would be greatly appreciated.