Magidoc

skipFinanceMigrationRow
Mutation

Leaves a failed migration row out of its import so the run can finish. The row keeps the result code and message explaining why it failed, and records who skipped it, when, and why; it stops being retried by the apply and is counted as skipped in the run's apply summary. Nothing brings it back: retrying a skipped row is refused and a requeue leaves it alone, so the row stays out for the life of the run. Access: signed-in members of the run's workspace with the setupUpdate permission, in a workspace where finance is enabled — the same gate retryFinanceMigrationRow asks for, because the two are the same decision about the same row. Errors: row not found in the named run; a row that is not failed (an applied, pending or already-skipped row has nothing to dispose of); an empty reason.

Arguments

#

migrationRunId

ID !
Non-null

rowId

ID !
Non-null

reason

Non-null

Why the row is being left out. Recorded on the row; kept to 500 characters.

Response

#

Returns FinanceMigrationRow !.

Example

#