Use the source records and status sequences supplied with each task. The review changes populations, owners and transient failures. A flow passes only when its visible effects and requested intermediate results agree with those independent fixtures. Preserve identifiers and unrelated columns while you change the approved field.
Some tasks require a specific retry policy. The count and interval are part of the operating request even when a faster retry would happen to succeed on one event. Others need Catch only after final failure and an audit on both the successful and recovered paths. Keep those outcomes distinct in the handoff.
All operations remain local. This practice cannot establish production access, live connector limits or safe retry behavior for an undocumented external write.
Connector response envelopes differ. Read the documented array, use the stable destination identifier for updates and preserve fields outside the approved patch. These actions use local rows rather than a signed-in enterprise account.