# Nosana job retries, executions and reward counting

Jobs, execution attempts and payments are not interchangeable row counts. A retry after a failure can belong to one job lifecycle. Two log entries alone do not establish two settled NOS rewards.

- Canonical: https://iotahome.site/en/learn/nosana-job-retry-counting
- Publisher: IOTA Watch
- Topics: Nosana
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

Jobs, execution attempts and payments are not interchangeable row counts. A retry after a failure can belong to one job lifecycle. Two log entries alone do not establish two settled NOS rewards.

## What to check

Match the node’s Solana address, Job ID, execution time and final state. Separate queued, running, failed and completed activity, then consult payment records for settled amounts. If a Job ID appears repeatedly, inspect its lifecycle before counting distinct jobs. Neither list length nor retries establish the node’s physical GPU count.

## Example

Example: an execution fails, then a retry completes. Preserve two events under one job identity. Payment eligibility and amount still require settlement evidence; multiplying event count by an assumed task price would overstate income.

## Continue

[Open project monitor](https://iotahome.site/en/projects/nosana)

## Sources and implementation

- [learn.nosana.com](https://learn.nosana.com/deployments/jobs/job_execution_flow)
- [dashboard.nosana.com](https://dashboard.nosana.com/)