Skip to content

Use of runAfterTS param is inconsistent #22

@mikeperley

Description

@mikeperley

The "publish message (channel, payload, runAfterTS)" public script seems to suggest "runAfterTS" to be the name of the key the user should set if they want to delay processing of the submitted message. However, usage of this value results in an empty runAfterTS field value of the resulting message. I believe the issue lies within line 18 of the "create message ( channel ; message ; runAfterTS )" script, where the Let statement expects a key of just "runAfter" and sets a local variable of "$runAfter" to that value. Additionally, line 47 of the same script sets the runAfterTS field to the value of $runAfterTS.

Updating the Let statement in line 18 to reference both the key "runAfterTS" and local variable "$runAfterTS" fixes the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions