[Latitude 5330] Suspend mode interrupted when close the lid

I have a newly installed manjaro with this strange behaviour: when I put it in suspend mode and then I close the lid the computer exits from suspend mode. I can see this from the battery level and from the heat coming from the back side.
How I could debug this problem?

This is my inxi -Fxi:

System:
  Host: pitone Kernel: 6.1.12-1-MANJARO arch: x86_64 bits: 64 compiler: gcc
    v: 12.2.1 Desktop: GNOME v: 43.3 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Latitude 5330 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 007WCW v: A00 serial: <superuser required> UEFI: Dell
    v: 1.9.0 date: 11/15/2022
Battery:
  ID-1: BAT0 charge: 36.6 Wh (63.1%) condition: 58.0/58.0 Wh (100.0%)
    volts: 15.5 min: 15.2 model: SMP DELL Y86WG26 status: discharging
CPU:
  Info: 10-core (2-mt/8-st) model: 12th Gen Intel Core i7-1265U bits: 64
    type: MST AMCP arch: Alder Lake rev: 4 cache: L1: 928 KiB L2: 6.5 MiB
    L3: 12 MiB
  Speed (MHz): avg: 2025 high: 2700 min/max: 400/4800:3600 cores: 1: 1334
    2: 2700 3: 2200 4: 2200 5: 1182 6: 2700 7: 752 8: 2700 9: 2700 10: 434
    11: 2700 12: 2700 bogomips: 64536
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] vendor: Dell
    driver: i915 v: kernel arch: Gen-12.2 bus-ID: 0000:00:02.0
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 3-6:2
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8
    compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Graphics (ADL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 0000:00:1f.3
  Sound API: ALSA v: k6.1.12-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.22 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3
  IF: wlp0s20f3 state: up mac: 8c:17:59:c8:2f:1c
  IP v4: 172.20.52.73/26 type: dynamic noprefixroute scope: global
  IP v6: fe80::bdf3:beed:363:dfd2/64 type: noprefixroute scope: link
  IF-ID-1: wg0 state: unknown speed: N/A duplex: N/A mac: N/A
  IF-ID-2: wwp0s20f0u1 state: down mac: 76:74:89:89:f5:6f
  WAN IP: 81.123.181.13
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 3-10:38
  Report: rfkill ID: hci0 rfk-id: 6 state: up address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 bus-ID: 0000:00:0e.0
Drives:
  Local Storage: total: 238.47 GiB used: 31.92 GiB (13.4%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN740 NVMe WD 256GB
    size: 238.47 GiB temp: 43.9 C
Partition:
  ID-1: / size: 93.1 GiB used: 30.98 GiB (33.3%) fs: ext4 dev: /dev/nvme0n1p8
  ID-2: /boot/efi size: 511 MiB used: 316 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 962.2 MiB (47.0%)
    dev: /dev/nvme0n1p7
Sensors:
  System Temperatures: cpu: 57.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 359 Uptime: 5d 19h 33m Memory: 15.32 GiB used: 9.55 GiB (62.4%)
  Init: systemd Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: 1438 Shell: Zsh
  v: 5.9 inxi: 3.3.25

Have you ever thought about the posibility, that closing the lid is the way your laptop goes into suspend mode?
Maybe because you put it in suspend mode prior to that, your laptop tries to wakeup instead, which might be a misconfiguration somewhere…
Which could be investigated by you using the journal logs…