When executing an Integrator job with limited user permissions in a database, it could happen that the job does not complete successfully due to missing permissions of the user. If in that case some write actions were already executed and others are still missing, the database could be in an inconsistent (and maybe unknown) state. This represents an unacceptable risk.
A solution to this problem could be to develop a check of the permissions of the current user to execute all job actions before the execution of the complete job.
This is particularly relevant as a roll-back of Integrator actions does not exist (see idea JS-I-1503).
This is specifically relevant and critical for legal consolidation and/or balance sheet projection models - we might have half-done consolidated data in the database.