Because the notification come ultimately from the SQLAlchemy before_commit hook it is possible for the Celery task to get the old details out of the database.
To fix in this extension would require sending all of the information to the task rather than looking it up. But this would mean that if the task takes some time to be scheduled that the information might be out of date.
Better solution might be to fix CKAN so that it fires the notification on the after_commit hook.
Because the notification come ultimately from the SQLAlchemy
before_commithook it is possible for the Celery task to get the old details out of the database.To fix in this extension would require sending all of the information to the task rather than looking it up. But this would mean that if the task takes some time to be scheduled that the information might be out of date.
Better solution might be to fix CKAN so that it fires the notification on the
after_commithook.