Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Boto: Simple Workflow decider schedules deprecated activity #1891

Open
sureshsaggar opened this Issue Dec 4, 2013 · 2 comments

Comments

Projects
None yet
2 participants

Hey Folks,

We're seeing failures because the SWF decider is trying to schedule a deprecated version of the some activity (here downloadfroms3). Although while making the decision in decider (i.e. a boto call to schedule_activity_task), we have set the VERSION as 3.0 and all our activities have been registered with the same version and can be seen from the AWS SWF console. Further sometimes the same activity in the workflow executes fine with the latest version while the next one will fail with ACTIVITY_TYPE_DEPRECATED error.

Boto Version = 2.14.0;

2013-12-03 00:47:39,949 - archimedes.s32oracle - INFO - ====================================================================================================
2013-12-03 00:47:39,949 - archimedes.s32oracle - INFO - # Version[3.0] Event[ScheduleActivityTaskFailed] Missing decision handler for the last event type...
2013-12-03 00:47:39,949 - archimedes.s32oracle - INFO - ====================================================================================================
2013-12-03 00:47:39,950 - django_root.s32oracle.commons - ERROR - {
    "eventId": 5,
    "eventTimestamp": 1386053259.829,
    "eventType": "ScheduleActivityTaskFailed",
    "scheduleActivityTaskFailedEventAttributes": {
        "activityId": "downloadfroms3-1386053259",
        "activityType": {
            "name": "downloadfroms3",
            "version": "2.0"
        },
        "cause": "ACTIVITY_TYPE_DEPRECATED",
        "decisionTaskCompletedEventId": 4
    }
}

Any insights? Besides, let me know if you need more information.

Regards,
Ss

@ghost ghost assigned danielgtaylor Dec 6, 2013

Owner

danielgtaylor commented Dec 6, 2013

I'm trying to reproduce this but am not quite sure how. I've run a few jobs with different activity type versions and it seems to work okay for me. Can you distill this down to a simple example or maybe describe some of the actions you took to get into the state your are in? A small piece of code to reliably produce the issue would be fantastic, but isn't required.

Probably obvious, but still worth asking in my opinion: is all your currently running code updated to use the latest activity type versions? Could something be producing or requesting jobs with the old version?

Thanks a lot for your reply. Will shortly get back to you with more details on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment