Canary deployment acknowledged but expires without processor report

[f0ff38]

Acurast support escalation hello canary execution (378420 378425)

Status: ready to open ticket В· network: Canary В· module: modules/hello

Hub (minimal 378425) | https://hub.acurast.com/job-detail/acurast-5CAG2e4hcYLoU6j1J27wrWU6pqGX4StyaDYEfmdvWfkCmRn7-378425 |

Questions for Acurast support

1. Processor 5GEr1Nd2XHHddsXjXrXtdQQVT3NnVrUeZB2hFXgpr1n19DBP acknowledged deployment 378425 but reported sla 0/1 before the window and no SLA after expiry did the Node.js bundle execute at all? Any crash/attestation/runtime rejection?
2. For a minimal one-shot job (HELLO_MINIMAL=1, only console.log, no network), what on-chain or Hub signals should we expect when execution succeeds?
3. With onlyAttestedDevices: false and maxAllowedStartDelayInMs: 60000, are there other processor-side gates (bundle size, Node runtime version, reputation) that block execution without failing acknowledgement?
4. DevTools API returned 502 from GitHub Actions (2026-06-13) is there an alternate API or Hub Reports export for processor stdout for job 378425?
5. Is this processor known healthy on Canary for other operators' Node.js deployments?

[f0ff38]

We reproduced the same pattern with an adapted official example workload.

Deployment: 378428
Run: https://github.com/f0ff38/nhmind/actions/runs/27526394107
Hub: https://hub.acurast.com/job-detail/acurast-5CAG2e4hcYLoU6j1J27wrWU6pqGX4StyaDYEfmdvWfkCmRn7-378428
Processor acked pre-window: 5E1yebdEpkmv5gD2UJs1jsb2sPzqNUa6oZHbiekwYxE4NLJ3
Pre-window: ack 1/1, sla 0/1
Post-window: Expired, ack 0/0

This deployment used an adapted Acurast example workload, not our Nostr/hello logic.
The bundle is only ~8.2 KB, with duration/max start delay both 300s, reward 0.05 cACU, requiredModules=[], onlyAttestedDevices=false.

Could you check processor/runtime logs for 378428 and confirm whether the Node.js bundle started at all, crashed before reporting, or failed to submit fulfillment?