Job listed terminates early - status listed as "Pause"

[hkelley]

** crackq.conf **

[jobtimeout]
# 3 weeks default
Value: 1814400
Modify: True

[misc]
#Maximum requeue attempts on failed job (only automatically retried jobs that failed due to system error, not user error)
req_max: 2
#Set the minimum number off cracked passwords required to generate a report
min_report: 100
#Allow hashcat warning messages (may cotain system filepaths and other info) to be returned to app users
user_warnings: False
# testing disable_brain because jobs disconnecting from hashcat prematurely
disable_brain: True

Describe the bug
Long-running (multi-hour) jobs are terminating early. The job shows up under the /complete view in the UI and the

and the API reports "Status": "finished", even though the hashcat stats say it is still running ("CrackQ State": "Pause",)

    "HC State":  {
                     "CrackQ State":  "Pause",
                     "HC State":  {
                                      "Brain Traffic (RX)":  "0 ",
                                      "Brain Traffic (TX)":  "0 ",
                                      "Cracked Hashes":  571,
                                      "Device Temperatures":  {
                                                                  "0":  75,
                                                                  "1":  77,
                                                                  "2":  77,
                                                                  "3":  77
                                                              },
                                      "ETA (Absolute)":  "Mon Nov 25 01:58:22 2024",
                                      "ETA (Relative)":  "2 hours, 16 mins",
                                      "HC Status":  "Running",
                                      "Progress":  51,
                                      "Rejected":  0,
                                      "Rejected Percentage":  0.0,
                                      "Restore Point":  4351590400,
                                      "Running Time":  8614971.159767,
                                      "Salts":  1,
                                      "Session":  "d478aabf398745809970c541c239f451",
                                      "Speed All":  "26054.2 M",
                                      "Speed Raw":  26054240111.607464,
                                      "Total Hashes":  7657
                                  },
                     "Speed Array":  [
....
                                     ],
                     "brain_check":  null,
                     "email":  "xxxxxcom",
                     "email_count":  0,
                     "last_seen":  "2024-11-24 21:00:00",
                     "notify":  false
                 },
    "Job Details":  {
                        "attack_mode":  "0",
                        "hash_mode":  "1000",
                        "increment":  "False",
                        "increment_max":  "None",
                        "increment_min":  "None",
                        "mask":  "None",
                        "name":  "ad hoc 202411242100 using template rockyou2021 with OneRule",
                        "restore":  "0",
                        "rules":  [
                                      "OneRule"
                                  ],
                        "username":  "False",
                        "wordlist":  "rockyou2021",
                        "wordlist2":  null
                    },
    "Result":  null,
    "Status":  "finished",
    "Time finished":  "2024-11-24 23:42:24.911324",
    "Time started":  "2024-11-24 21:00:15.086837"
}

To Reproduce

1. Run a long job. I am testing further now to see if the job runs to completion when no other jobs are submitted/queued while running.

Expected behavior

• Job should not report as "finished" if it is actually paused.