Auth0 Triggers not bound in UI

Help
,
1

I’ve created a action and trigger via the Auth0 API for the machine to machine flow. Both the trigger and action for credentials-exchange are created correctly and I can view the Action in the Actions tab on the UI. However, the trigger is not bound in the UI when I view the machine to machine flow. I’ve called the GET /api/v2/actions/triggers/credentials-exchange/bindings API and I can see that the created action is bound to the trigger. But like I said, I don’t see that reflected in the UI.

{
  "bindings": [
    {
      "id": "bce6cc34-d901-4716-aff6-58ba0d07bdbb",
      "trigger_id": "credentials-exchange",
      "action": {
        "id": "4ac14f38-501c-4e0a-8ff8-05f6450c4345",
        "name": "AugmentClaims",
        "supported_triggers": [
          {
            "id": "credentials-exchange",
            "version": "v2"
          }
        ],
        "created_at": "2024-04-19T20:01:37.822434931Z",
        "updated_at": "2024-04-19T20:44:35.591617906Z",
        "current_version": {
          "id": "40ecf177-3ab1-43e7-a8d8-0b9f3dc043ab",
          "code": "\n                        exports.onExecuteCredentialsExchange = async (event, api) => {\n                          api.accessToken.setCustomClaim('companyId', event.client.metadata.companyId);\n                          api.accessToken.setCustomClaim('companyType', event.client.metadata.companyType);\n                        };\n                    ",
          "runtime": "node18-actions",
          "status": "BUILT",
          "number": 5,
          "build_time": "2024-04-19T20:44:35.966777537Z",
          "created_at": "2024-04-19T20:44:35.896171160Z",
          "updated_at": "2024-04-19T20:44:35.967272927Z"
        },
        "deployed_version": {
          "code": "\n                        exports.onExecuteCredentialsExchange = async (event, api) => {\n                          api.accessToken.setCustomClaim('companyId', event.client.metadata.companyId);\n                          api.accessToken.setCustomClaim('companyType', event.client.metadata.companyType);\n                        };\n                    ",
          "dependencies": [],
          "id": "40ecf177-3ab1-43e7-a8d8-0b9f3dc043ab",
          "deployed": true,
          "number": 5,
          "built_at": "2024-04-19T20:44:35.966777537Z",
          "secrets": [],
          "status": "built",
          "created_at": "2024-04-19T20:44:35.896171160Z",
          "updated_at": "2024-04-19T20:44:35.967272927Z",
          "runtime": "node18-actions",
          "supported_triggers": [
            {
              "id": "credentials-exchange",
              "version": "v2"
            }
          ]
        },
        "all_changes_deployed": false
      },
      "created_at": "2024-04-19T20:01:50.818580200Z",
      "updated_at": "2024-04-19T23:30:28.563403325Z"
    }
  ],
  "total": 1,
  "per_page": 20
}

Additionally, if I manually attach that action via the UI to the machine to machine flow, I now see two bindings when I call the API mentioned above.

Am I missing a step in the process to add this action to the machine to machine flow via the API?