User story #6646: Document status for unknow return code in jobscheduler technique - Rudder - Issue Tracker

Actions

User story #6646

open

Document status for unknow return code in jobscheduler technique

Added by Benoît PECCATTE over 9 years ago. Updated almost 7 years ago.

Status:

New

Priority:

N/A

Assignee:

-

Category:

Techniques

Target version:

Ideas (not version specific)

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

In the jobScheduler technique, it is possible to interpret different return code into different status.
But the 3 statuses are given (kept, repaired and error) which means we have to explicitly list all return codes.
What is the default status for codes not listed ? and if it is an error we need a way to list all codes in a simple way.

Actions

#1

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.10.15 to 2.10.16

Actions

#2

Updated by Vincent MEMBRÉ over 9 years ago

Target version changed from 2.10.16 to 2.10.17

Actions

#3

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 2.10.17 to 2.10.18

Actions

#4

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 2.10.18 to 2.10.19

Actions

#5

Updated by Vincent MEMBRÉ about 9 years ago

Target version changed from 2.10.19 to 2.10.20

Actions

#6

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 2.10.20 to 277

Actions

#7

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 277 to 2.11.18

Actions

#8

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 2.11.18 to 2.11.19

Actions

#9

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.19 to 2.11.20

Actions

#10

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.20 to 2.11.21

Actions

#11

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.21 to 2.11.22

Actions

#12

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.22 to 2.11.23

Actions

#13

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 2.11.23 to 2.11.24

Actions

#14

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 2.11.24 to 308

Actions

#15

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 308 to 3.1.14

Actions

#16

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.14 to 3.1.15

Actions

#17

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.15 to 3.1.16

Actions

#18

Updated by Vincent MEMBRÉ about 8 years ago

Target version changed from 3.1.16 to 3.1.17

Actions

#19

Updated by Vincent MEMBRÉ almost 8 years ago

Target version changed from 3.1.17 to 3.1.18

Actions

#20

Updated by Vincent MEMBRÉ almost 8 years ago

Target version changed from 3.1.18 to 3.1.19

Actions

#21

Updated by Benoît PECCATTE over 7 years ago

Tracker changed from Bug to User story

Actions

#22

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.19 to 3.1.20

Actions

#23

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.20 to 3.1.21

Actions

#24

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.21 to 3.1.22

Actions

#25

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 3.1.22 to 3.1.23

Actions

#26

Updated by Vincent MEMBRÉ about 7 years ago

Target version changed from 3.1.23 to 3.1.24

Actions

#27

Updated by Vincent MEMBRÉ about 7 years ago

Target version changed from 3.1.24 to 3.1.25

Actions

#28

Updated by Benoît PECCATTE about 7 years ago

Target version changed from 3.1.25 to 4.1.9

Actions

#29

Updated by Vincent MEMBRÉ almost 7 years ago

Target version changed from 4.1.9 to 4.1.10

Actions

#30

Updated by Benoît PECCATTE almost 7 years ago

Target version changed from 4.1.10 to Ideas (not version specific)

Actions

Also available in: Atom PDF