getting archive workflows not working

[TimSchSkaylink]

Describe the bug

After adding needed values like explained in the docu for "Workflow Archive" workflows getting archived into the database is working, but they dont show up in the UI. From api perspective i'm geeting different responds. If i call /api/v1/archived-workflows i get {"metadata":{},"items":null} If i call /api/v1/archived-workflows/<uid> i get {"code":2,"message":"getting archived workflows not supported"}

I saw issue 323 and it seems like i have the same issues like explained there but i have persistence.archive true in my configmap

Related helm chart

argo-workflows

To Reproduce

1. Running argo-workflows inside aks
2. Create postgres pod in same namespace
3. Create aks secret in same namespace with values password:<postgrespassword> and username: <postgresusername>
4. Add persistence under data in workflow configmap

persistence: |
    archive: true
    postgresql:
      host: postgres.argo.svc.cluster.local
      port: 5432
      database: postgresdb
      tableName: argo_workflows
      userNameSecret:
        name: <SecretNameFromStep3>
        key: username
      passwordSecret:
        name: <SecretNameFromStep3>
        key: password

Expected behavior

I would expect the UI and API is now showing the archived workflows. And that the api endpoints are giving back the same error codes if not configured correctly.

Screenshots

No response

Additional context

argo workflow version: v3.2.4

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[TimSchSkaylink]

Still not working, also tested after redployment.

[MandeepAtLark]

@TimSchSkaylink are you able to see your workflows in the database?

[TimSchSkaylink]

@MandeepAtLark Yes, the workflows getting saved in the database

[MandeepAtLark]

Thank you for replying @TimSchSkaylink not sure why I am not able to save in Postgres.

[makzzz1986]

To be deleted. After restart of an argo-server it connected to a database 🤔

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[deepupv]

I still face this issue. the workflow is saved in db, but the UI does not display it. it displayed the message " Unsuccessful HTTP response: getting archived workflows not supported" instead