Originally I thought we could just add arbitrary tags/arguments to a state signal. The code I had in place before just created a signal message that looked like: "{'message': 'No new source data. Skipping...', 'etag_skip_flag': True}" (note that it's just one big string 🤦). So, there never was an etag_skip_flag attribute to look for, meaning the final flow state would never be set to Skipped.
To fix this, this now modifies the signal's context and adds the etag_skip_flag to this dictionary.
My local testing must have been slightly different to not catch this :/
Originally I thought we could just add arbitrary tags/arguments to a state signal. The code I had in place before just created a signal message that looked like:
"{'message': 'No new source data. Skipping...', 'etag_skip_flag': True}"(note that it's just one big string 🤦). So, there never was anetag_skip_flagattribute to look for, meaning the final flow state would never be set toSkipped.To fix this, this now modifies the signal's context and adds the
etag_skip_flagto this dictionary.My local testing must have been slightly different to not catch this :/